Resource management for beam failure recovery procedures

ABSTRACT

Wireless communications are described. A wireless device and/or a base station may provide improved resource management. A base station may configure and/or transmit a beam failure recovery medium access control control element (BFR MAC CE) to a wireless device to configure particular cells to use particular assigned candidate beams from a pool of shared candidate beams during beam failure recovery operations. The BFR MAC CE may provide orthogonality in beams that may be designated for use by active cells out of a shared pool of beams that may not be orthogonal across all potentially available cells.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/716,817, titled “Resource Management in Beam Failure RecoveryProcedure” and filed on Aug. 9, 2018. The above-referenced applicationis hereby incorporated by reference in its entirety.

BACKGROUND

Wireless communications may use bandwidth parts (BWPs) and/or otherwireless resources. Random access procedures may be performed, forexample, between a base station and a wireless device. Beamforming maybe used to establish beams for directional signal transmission and/orreception in wireless communications.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Wireless communications may use random access procedures and beamformingto increase overall network communications data throughput and reducecommunications channel interference. A device (e.g., a wireless deviceand/or a base station) may perform beamforming to focus communicationsin a cell. Beamforming may be performed based on configurationparameters sent from a base station to a wireless device. If a beamfails, a beam failure recovery (BFR) procedure may be performed todetermine a new set of orthogonal beamforming parameter specificationsand form a new beam between the wireless device and a base station. Thenumber/quantity of supported independent beams and the quantity ofsupported beamforming parameter specifications may impact the resourcerequirements and/or resource management of beam failure recoveryprocedures. A BFR medium access control control element (MAC CE) may besent by a base station to a wireless device that may include at leastone BFR request resource. The wireless device may use the received atleast one beam failure recovery request resource to determine to performand/or initiate a random access procedure for performing beam failurerecovery based on detecting a beam failure. The BFR MAC CE may allocatebeam failure recovery resources to particular cells to achieveorthogonality of resource allocation, for example, by specifyingparticular combinations of random access preambles and time-frequencyresource allocations of beams to be used by particular cells, BWPs,and/or other wireless resources. The base station may assign the BFRresources to be used by particular cells according to the BFR MAC CEwhich may prevent conflicts. Fewer unique BFR resources may be used by agroup of cells, and orthogonality between beams assigned to the cellsmay be achieved, by using the BFR MAC CE to uniquely assign the BFRresources from shared resources to particular cells. Fewer unique BFRresources allocated may reduce computational complexity, reduce powerconsumption, improve system efficiency, and/or improve deviceperformance.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A, FIG. 16B and FIG. 16C show examples of MAC subheaders.

FIG. 17A and FIG. 17B show examples of MAC PDUs.

FIG. 18 shows an example of LCIDs for DL-SCH.

FIG. 19 shows an example of LCIDs for UL-SCH.

FIG. 20A and FIG. 20B show examples of secondary cell (SCell)Activation/Deactivation MAC CE.

FIG. 21A shows an example of an SCell hibernation MAC control element(CE).

FIG. 21B shows an example of an SCell hibernation MAC CE.

FIG. 21C shows an example of MAC CEs for SCell state transitions.

FIG. 22 shows an example of SCell state transition.

FIG. 23 shows an example of SCell state transition.

FIG. 24A and FIG. 24B show examples of beam failure scenarios.

FIG. 25 shows an example of a beam failure recovery (BFR) procedure.

FIG. 26 shows an example of downlink beam failure instance indication.

FIG. 27 shows an example of a resource configuration for a downlink beamfailure recovery procedure.

FIG. 28 shows an example of a resource configuration for a downlink beamfailure recovery procedure.

FIG. 29A and FIG. 29B show example MAC CE designs for downlink beamfailure recovery procedures.

FIG. 30 shows an example of a downlink beam failure recovery procedure.

FIG. 31A and FIG. 31B show example MAC CE designs for downlink beamfailure recovery procedures.

FIG. 32 shows an example of a resource configuration for a downlink beamfailure recovery procedure.

FIG. 33A, FIG. 33B, and FIG. 33C show example MAC CE designs fordownlink beam failure recovery procedures.

FIG. 34 shows an example of MAC CE design for downlink beam failurerecovery procedure.

FIG. 35 shows an example of MAC CE design for downlink beam failurerecovery procedure.

FIG. 36 shows an example of a downlink beam failure recovery procedure.

FIG. 37 shows an example of a downlink beam failure recovery procedure.

FIG. 38 shows an example flowchart of a downlink beam failure recoveryprocedure.

FIG. 39 shows an example flowchart of a downlink beam failure recoveryprocedure.

FIG. 40 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto resource management for beam failure recovery procedures for wirelesscommunications.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BPSK Binary Phase Shift Keying

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CE Control Element

CN Core Network

CORESET Control Resource Set

CP Cyclic Prefix

CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CRI CSI-RS resource indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control Channel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic Channel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolved-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCID Logical Channel Identifier

LI Layer Indicator

LTE Long Term Evolution

MAC Medium Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node j

NACK Negative Acknowledgement

NAS Non-Access Stratum

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-eNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NR PDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM Orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PMI Precoding Matrix Indicator

PRACH Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QCLed Quasi-Co-Located

QCL Quasi-Co-Location

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank indicator

RLC Radio Link Control

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SC-FDMA Single Carrier-Frequency Division Multiple Access

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number

S-GW Serving GateWay

SI System Information

SIB System Information Block

SINR Signal-to-Interference-plus-Noise Ratio

SMF Session Management Function

SN Secondary Node

SpCell Special Cell

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSB Synchronization Signal Block

SSBRI Synchronization Signal Block Resource Indicator

SSS Secondary Synchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance

TAG Timing Advance Group

TAI Tracking Area Identifier

TAT Time Alignment Timer

TB Transport Block

TC-RNTI Temporary Cell-Radio Network Temporary Identifier

TCI Transmission Configuration Indication

TDD Time Division Duplex

TDMA Time Division Multiple Access

TRP Transmission Reception Point

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared CHannel

UPF User Plane Function

UPGW User Plane Gateway

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, 1024-QAM and/or the like. Physical radio transmission may beenhanced by dynamically or semi-dynamically changing the modulation andcoding scheme, for example, depending on transmission requirementsand/or radio conditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface. The wirelessdevices 110A and/or 110B may be structurally similar to wireless devicesshown in and/or described in connection with other drawing figures. TheNode B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120Dmay be structurally similar to Nodes B and/or base stations shown inand/or described in connection with other drawing figures.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Medium Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A wireless device (e.g., a MAC entity ofthe wireless device) may support one or multiple numerologies and/ortransmission timings. Mapping restrictions in a logical channelprioritization may control which numerology and/or transmission timing alogical channel may use. An RLC sublayer may support transparent mode(TM), unacknowledged mode (UM), and/or acknowledged mode (AM)transmission modes. The RLC configuration may be per logical channelwith no dependency on numerologies and/or Transmission Time Interval(TTI) durations. Automatic Repeat Request (ARQ) may operate on any ofthe numerologies and/or TTI durations with which the logical channel isconfigured. Services and functions of the PDCP layer for the user planemay comprise, for example, sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g., such as for split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. Services and/or functionsof SDAP may comprise, for example, mapping between a QoS flow and a dataradio bearer. Services and/or functions of SDAP may comprise mapping aQuality of Service Indicator (QFI) in DL and UL packets. A protocolentity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MAC CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs indicating one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterInformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signalling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A, FIG. 7B,FIG. 8, and associated text, described below.

Other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SS/PBCH blocks, forexample, if the downlink CSI-RS 522 and SS/PBCH blocks are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are outside of the PRBs configured for the SS/PBCH blocks.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time for acarrier. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers (such as forcarrier aggregation) or ranging from 1 to 64 carriers (such as for dualconnectivity). Different radio frame structures may be supported (e.g.,for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. Radio frame duration may be 10 milliseconds (ms). A 10 msradio frame 601 may be divided into ten equally sized subframes 602,each with a 1 ms duration. Subframe(s) may comprise one or more slots(e.g., slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Other subframe durations such as, for example, 0.5 ms, 1 ms, 2ms, and 5 ms may be supported. Uplink and downlink transmissions may beseparated in the frequency domain. Slot(s) may include a plurality ofOFDM symbols 604. The number of OFDM symbols 604 in a slot 605 maydepend on the cyclic prefix length. A slot may be 14 OFDM symbols forthe same subcarrier spacing of up to 480 kHz with normal CP. A slot maybe 12 OFDM symbols for the same subcarrier spacing of 60 kHz withextended CP. A slot may comprise downlink, uplink, and/or a downlinkpart and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activatethe CS resources. The DCI may comprise parameters indicating that theuplink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC message, TheCS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) DCI comprising a slotformat indicator (SFI) indicating a slot format. The base station maysend (e.g., transmit) DCI comprising a preemption indication indicatingthe PRB(s) and/or OFDM symbol(s) in which a wireless device may assumeno transmission is intended for the wireless device. The base stationmay send (e.g., transmit) DCI for group power control of the PUCCH, thePUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless devicemay obtain an RNTI after or in response to completing the initial access(e.g., C-RNTI). The base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute)an RNTI (e.g., the wireless device may determine the RA-RNTI based onresources used for transmission of a preamble). An RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device maymonitor a group common search space which may be used by the basestation for sending (e.g., transmitting) DCIs that are intended for agroup of wireless devices. A group common DCI may correspond to an RNTIwhich is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP. BWPs are describedas example resources. Any wireless resource may be applicable to one ormore procedures described herein.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a wireless device is configured with a secondary carrier on a primarycell, the wireless device may be configured with an initial BWP forrandom access procedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base station may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may refrain fromconfiguring a wireless device without a common search space on a PCell,or on a PSCell, in an active DL BWP. For an UL BWP in a set of one ormore UL BWPs, a base station may configure a wireless device with one ormore resource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided with a default DL BWP, a default BWP may be aninitial active DL BWP. A default BWP may not be configured for one ormore wireless devices. A first (or initial) BWP may serve as a defaultBWP, for example, if a default BWP is not configured.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be de-activated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice. A master base station may determine (e.g., based on receivedmeasurement reports, traffic conditions, and/or bearer types) to requesta secondary base station to provide additional resources (e.g., servingcells) for a wireless device. After or upon receiving a request from amaster base station, a secondary base station may create and/or modify acontainer that may result in a configuration of additional serving cellsfor a wireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg1 1220 and Msg3 1240 of a four-step random accessprocedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery procedure and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on a beam failure recovery procedure, and/or a contentionresolution timer.

The Msg 1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a beam failurerecovery procedure associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for a beam failure recovery procedure, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a beam failure recovery procedure. Thewireless device may determine an RA-RNTI at least based on an index of afirst OFDM symbol, an index of a first slot of a selected PRACHoccasions, and/or an uplink carrier index for a transmission of Msg11220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230.

The wireless device may start a time window (e.g., ra-ResponseWindow) tomonitor a random access response. For a beam failure recovery procedure,the base station may configure the wireless device with a different timewindow (e.g., bfr-ResponseWindow) to monitor response to on a beamfailure recovery request. The wireless device may start a time window(e.g., ra-ResponseWindow or bfr-ResponseWindow) at a start of a firstPDCCH occasion, for example, after a fixed duration of one or moresymbols from an end of a preamble transmission. If the wireless devicesends (e.g., transmits) multiple preambles, the wireless device maystart a time window at a start of a first PDCCH occasion after a fixedduration of one or more symbols from an end of a first preambletransmission. The wireless device may monitor a PDCCH of a cell for atleast one random access response identified by a RA-RNTI, or for atleast one response to a beam failure recovery request identified by aC-RNTI, at a time that a timer for a time window is running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). Awireless device (e.g., a MAC entity of the wireless device) may handle arandom access process (e.g., Random Access Control 1354 and/or RandomAccess Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may communicate with a wireless device via a wirelessnetwork using one or more technologies, such as new radio technologies(e.g., NR, 5G, etc.). The one or more radio technologies may comprise atleast one of: multiple technologies related to physical layer; multipletechnologies related to medium access control layer; and/or multipletechnologies related to radio resource control layer Enhancing the oneor more radio technologies may improve performance of a wirelessnetwork. System throughput, and/or data rate of transmission, may beincreased. Battery consumption of a wireless device may be reduced.Latency of data transmission between a base station and a wirelessdevice may be improved. Network coverage of a wireless network may beimproved. Transmission efficiency of a wireless network may be improved.

A base station may send (e.g., transmit) DCI via a PDCCH for at leastone of: a scheduling assignment and/or grant; a slot formatnotification; a preemption indication; and/or a power-control command.The DCI may comprise at least one of: an identifier of a DCI format; adownlink scheduling assignment(s); an uplink scheduling grant(s); a slotformat indicator; a preemption indication; a power-control forPUCCH/PUSCH; and/or a power-control for SRS.

A downlink scheduling assignment DCI may comprise parameters indicatingat least one of: an identifier of a DCI format; a PDSCH resourceindication; a transport format; HARQ information; control informationrelated to multiple antenna schemes; and/or a command for power controlof the PUCCH. An uplink scheduling grant DCI may comprise parametersindicating at least one of: an identifier of a DCI format; a PUSCHresource indication; a transport format; HARQ related information;and/or a power control command of the PUSCH.

Different types of control information may correspond to different DCImessage sizes. Supporting multiple beams, spatial multiplexing in thespatial domain, and/or noncontiguous allocation of RBs in the frequencydomain, may require a larger scheduling message, in comparison with anuplink grant allowing for frequency-contiguous allocation. DCI may becategorized into different DCI formats. A DCI format may correspond to acertain message size and/or usage.

A wireless device may monitor (e.g., in common search space or wirelessdevice-specific search space) one or more PDCCH for detecting one ormore DCI with one or more DCI format. A wireless device may monitor aPDCCH with a limited set of DCI formats, for example, which may reducepower consumption. The more DCI formats that are to be detected, themore power may be consumed by the wireless device.

The information in the DCI formats for downlink scheduling may compriseat least one of: an identifier of a DCI format; a carrier indicator; anRB allocation; a time resource allocation; a bandwidth part indicator; aHARQ process number; one or more MCS; one or more NDI; one or more RV;MIMO related information; a downlink assignment index (DAI); a TPC forPUCCH; an SRS request; and/or padding (e.g., if necessary). The MIMOrelated information may comprise at least one of: a PMI; precodinginformation; a transport block swap flag; a power offset between PDSCHand a reference signal; a reference-signal scrambling sequence; a numberof layers; antenna ports for the transmission; and/or a transmissionconfiguration indication (TCI).

The information in the DCI formats used for uplink scheduling maycomprise at least one of: an identifier of a DCI format; a carrierindicator; a bandwidth part indication; a resource allocation type; anRB allocation; a time resource allocation; an MCS; an NDI; a phaserotation of the uplink DMRS; precoding information; a CSI request; anSRS request; an uplink index/DAI; a TPC for PUSCH; and/or padding (e.g.,if necessary).

A base station may perform CRC scrambling for DCI, for example, beforetransmitting the DCI via a PDCCH. The base station may perform CRCscrambling by binarily adding multiple bits of at least one wirelessdevice identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, SP CSI C-RNTI, and/or TPC-SRS-RNTI) on the CRC bits ofthe DCI. The wireless device may check the CRC bits of the DCI, forexample, if detecting the DCI. The wireless device may receive the DCI,for example, if the CRC is scrambled by a sequence of bits that is thesame as the at least one wireless device identifier.

A base station may send (e.g., transmit) one or more PDCCH in differentCORESETs, for example, to support a wide bandwidth operation. A basestation may transmit one or more RRC messages comprising configurationparameters of one or more CORESETs. A CORESET may comprise at least oneof: a first OFDM symbol; a number of consecutive OFDM symbols; a set ofresource blocks; and/or a CCE-to-REG mapping. A base station may send(e.g., transmit) a PDCCH in a dedicated CORESET for particular purpose,for example, for beam failure recovery confirmation. A wireless devicemay monitor a PDCCH for detecting DCI in one or more configuredCORESETs, for example, to reduce the power consumption.

A base station may send (e.g., transmit) one or more MAC PDUs to awireless device. A MAC PDU may comprise a bit string that may be bytealigned (e.g., multiple of eight bits) in length. Bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. The bit string may be readfrom the left to right, and then, in the reading order of the lines. Thebit order of a parameter field within a MAC PDU may be represented withthe first and most significant bit in the leftmost bit, and with thelast and least significant bit in the rightmost bit.

A MAC SDU may comprise a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC SDU may be included in a MAC PDU, forexample, from the first bit onward. In an example, a MAC CE may be a bitstring that is byte aligned (e.g., multiple of eight bits) in length. AMAC subheader may be a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC subheader may be placed immediately infront of the corresponding MAC SDU, MAC CE, and/or padding. A wirelessdevice (e.g., a MAC entity of the wireless device) may ignore a value ofreserved bits in a DL MAC PDU.

A MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the oneor more MAC subPDUs may comprise at least one of: a MAC subheader only(e.g., including padding); a MAC subheader and a MAC SDU; a MACsubheader and a MAC CE; and/or a MAC subheader and padding. The MAC SDUmay be of variable size. A MAC subheader may correspond to a MAC SDU, aMAC CE, and/or padding.

A MAC subheader may comprise: an R field comprising one bit; an F fieldwith one bit in length; an LCID field with multiple bits in length; an Lfield with multiple bits in length, for example, if the MAC subheadercorresponds to a MAC SDU, a variable-sized MAC CE, and/or padding.

FIG. 16A shows an example of a MAC subheader comprising an eight-bit Lfield. The LCID field may have six bits in length. The L field may haveeight bits in length.

FIG. 16B shows an example of a MAC subheader with a sixteen-bit L field.The LCID field may have six bits in length. The L field may have sixteenbits in length. A MAC subheader may comprise: a R field comprising twobits in length; and an LCID field comprising multiple bits in length(e.g., if the MAC subheader corresponds to a fixed sized MAC CE), and/orpadding.

FIG. 16C shows an example of the MAC subheader. The LCID field maycomprise six bits in length, and the R field may comprise two bits inlength.

FIG. 17A shows an example of a DL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising MAC CE may be placed before anyMAC subPDU comprising a MAC SDU, and/or before a MAC subPDU comprisingpadding.

FIG. 17B shows an example of a UL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising a MAC CE may be placed afterall MAC subPDU comprising a MAC SDU. The MAC subPDU may be placed beforea MAC subPDU comprising padding.

FIG. 18 shows first examples of LCIDs. FIG. 19 shows second examples ofLCIDs. In each of FIG. 18 and FIG. 19, the left columns compriseindices, and the right columns comprises corresponding LCID values foreach index.

FIG. 18 shows an example of an LCID that may be associated with the oneor more MAC CEs. A MAC entity of a base station may send (e.g.,transmit) to a MAC entity of a wireless device one or more MAC CEs. Theone or more MAC CEs may comprise at least one of: an SP ZP CSI-RSResource Set Activation/Deactivation MAC CE; a PUCCH spatial relationActivation/Deactivation MAC CE; a SP SRS Activation/Deactivation MAC CE;a SP CSI reporting on PUCCH Activation/Deactivation MAC CE; a TCI StateIndication for UE-specific PDCCH MAC CE; a TCI State Indication forUE-specific PDSCH MAC CE; an Aperiodic CSI Trigger State SubselectionMAC CE; a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE;a wireless device (e.g., UE) contention resolution identity MAC CE; atiming advance command MAC CE; a DRX command MAC CE; a long DRX commandMAC CE; an SCell activation and/or deactivation MAC CE (e.g., 1 Octet);an SCell activation and/or deactivation MAC CE (e.g., 4 Octet); and/or aduplication activation and/or deactivation MAC CE. A MAC CE may comprisean LCID in the corresponding MAC subheader. Different MAC CEs may havedifferent LCID in the corresponding MAC subheader. An LCID with 111011in a MAC subheader may indicate a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

FIG. 19 shows further examples of LCIDs associated with one or more MACCEs. The MAC entity of the wireless device may send (e.g., transmit), tothe MAC entity of the base station, one or more MAC CEs. The one or moreMAC CEs may comprise at least one of: a short buffer status report (BSR)MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grantconfirmation MAC CE; a single entry power headroom report (PHR) MAC CE;a multiple entry PHR MAC CE; a short truncated BSR; and/or a longtruncated BSR. A MAC CE may comprise an LCID in the corresponding MACsubheader. Different MAC CEs may have different LCIDs in thecorresponding MAC subheader. The LCID with 111011 in a MAC subheader mayindicate a MAC CE associated with the MAC subheader is a short-truncatedcommand MAC CE.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising ansCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., ansCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., ansCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the timer (e.g.,sCellDeactivationTimer timer) associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may clear one or more configured downlink assignmentsand/or one or more configured uplink grant Type 2 associated with theactivated SCell, for example, after or in response to the deactivatingthe activated SCell. The wireless device may suspend one or moreconfigured uplink grant Type 1 associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may flush HARQ buffers associated with the activatedSCell.

A wireless device may refrain from performing certain operations, forexample, if an SCell is deactivated. The wireless device may refrainfrom performing one or more of the following operations if an SCell isdeactivated: transmitting SRS on the SCell; reporting CQI, PMI, RI,and/or CRI for the SCell on a PCell; transmitting on UL-SCH on theSCell; transmitting on a RACH on the SCell; monitoring at least onefirst PDCCH on the SCell; monitoring at least one second PDCCH for theSCell on the PCell; and/or transmitting a PUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated SCell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., ansCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

FIG. 20A shows an example of an SCell activation/deactivation MAC CEthat may comprise one octet. A first MAC PDU subheader comprising afirst LCID may identify the SCell activation/deactivation MAC CE of oneoctet. An SCell activation/deactivation MAC CE of one octet may have afixed size. The SCell activation/deactivation MAC CE of one octet maycomprise a single octet. The single octet may comprise a first number ofC-fields (e.g., seven) and a second number of R-fields (e.g., one).

FIG. 20B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID may identifythe SCell Activation/Deactivation MAC CE of four octets. An SCellactivation/deactivation MAC CE of four octets may have a fixed size. TheSCell activation/deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1). A C_(i) field mayindicate an activation/deactivation status of an SCell with an SCellindex i, for example, if an SCell with SCell index i is configured. AnSCell with an SCell index i may be activated, for example, if the C_(i)field is set to one. An SCell with an SCell index i may be deactivated,for example, if the C_(i) field is set to zero. The wireless device mayignore the C_(i) field, for example, if there is no SCell configuredwith SCell index i. An R field may indicate a reserved bit. The R fieldmay be set to zero.

A base station and/or a wireless device may use a power saving mechanism(e.g., hibernation mechanism) of an SCell, for example, if CA isconfigured. A power saving mechanism may improve battery performance(e.g., run-times), reduce power consumption of the wireless device,and/or expedite SCell activation and/or SCell addition. The SCell may betransitioned (e.g., switched and/or adjusted) to dormant state if thewireless device initiates a power saving state for (e.g., hibernates)the SCell. The wireless device may, for example, if the SCell istransitioned to dormant state: stop transmitting SRS on the SCell,report CQI/PMI/RI/PTI/CRI for the SCell according to or based on aperiodicity configured for the SCell in dormant state, not transmit onan UL-SCH on the SCell, not transmit on a RACH on the SCell, not monitorthe PDCCH on the SCell, not monitor the PDCCH for the SCell, and/or nottransmit PUCCH on the SCell. Not transmitting, not monitoring, notreceiving, and/or not performing an action may comprise, for example,refraining from transmitting, refraining from monitoring, refrainingfrom receiving, and/or refraining from performing an action,respectively. Reporting CSI for an SCell, that has been transitioned toa dormant state, and not monitoring the PDCCH on/for the SCell, mayprovide the base station an “always-updated” CSI for the SCell. The basestation may use a quick and/or accurate channel adaptive scheduling onthe SCell, based on the always-updated CSI, if the SCell is transitionedback to active state. Using the always-updated CSI may speed up anactivation procedure of the SCell. Reporting CSI for the SCell and notmonitoring the PDCCH on and/or for the SCell (e.g., that may have beentransitioned to a dormant state), may provide advantages such asincreased battery efficiency, reduced power consumption of the wirelessdevice, and/or increased timeliness and/or accuracy of channel feedbackinformation feedback. A PCell/PSCell and/or a PUCCH SCell, for example,may not be configured or transitioned to a dormant state.

A base station may activate, hibernate, or deactivate at least one ofone or more configured SCells. A base station may send (e.g., transmit)to a wireless device, for example, one or more messages comprisingparameters indicating at least one SCell being set to an active state, adormant state, or an inactive state. A base station may transmit, forexample, one or more RRC messages comprising parameters indicating atleast one SCell being set to an active state, a dormant state, or aninactive state. A base station may transmit, for example, one or moreMAC control elements (CEs) comprising parameters indicating at least oneSCell being set to an active state, a dormant state, or an inactivestate.

The wireless device may perform (e.g., if the SCell is in an activestate): SRS transmissions on the SCell, CQI/PMI/RI/CRI reporting for theSCell, PDCCH monitoring on the SCell, PDCCH monitoring for the SCell,and/or PUCCH/SPUCCH transmissions on the SCell. The wireless device may(e.g., if the SCell is in an inactive state): not transmit SRS on theSCell, not report CQI/PMI/RI/CRI for the SCell, not transmit on anUL-SCH on the SCell, not transmit on a RACH on the SCell, not monitorPDCCH on the SCell, not monitor a PDCCH for the SCell; and/or nottransmit a PUCCH/SPUCCH on the SCell. The wireless device may (e.g., ifthe SCell is in dormant state): not transmit SRS on the SCell, reportCQI/PMI/RI/CRI for the SCell, not transmit on a UL-SCH on the SCell, nottransmit on a RACH on the SCell, not monitor a PDCCH on the SCell, notmonitor a PDCCH for the SCell, and/or not transmit a PUCCH/SPUCCH on theSCell.

A base station may send (e.g., transmit), for example, a first MAC CE(e.g., an activation/deactivation MAC CE). The first MAC CE mayindicate, to a wireless device, activation or deactivation of at leastone SCell. A C_(i) field may indicate an activation/deactivation statusof an SCell with an SCell index i, for example, if an SCell with SCellindex i is configured. An SCell with an SCell index i may be activated,for example, if the C_(i) field is set to one. An SCell with an SCellindex i may be deactivated, for example, if the C_(i) field is set tozero. A wireless device receiving a MAC CE may ignore the C_(i) field,for example, if there is no SCell configured with SCell index i. An Rfield may indicate a reserved bit. The R field may be set to zero.

A base station may transmit a MAC CE (e.g., a hibernation MAC CE) thatmay generally be referred to herein as a second MAC CE. The second MACCE may be the same as or different from other MAC CEs described herein,but is generally referred to herein as the second MAC CE. The second MACCE may indicate activation and/or hibernation of at least one SCell to awireless device. The second MAC CE may be associated with, for example,a second LCID different from a first LCID of the first MAC CE (e.g., theactivation/deactivation MAC CE). The second MAC CE may have a fixedsize. The second MAC CE may comprise a single octet comprising sevenC-fields and one R-field.

FIG. 21A shows an example of a MAC CE (e.g., the second MAC CEreferenced above) comprising a single octet. The second MAC CE maycomprise four octets comprising 31 C-fields and one R-field. FIG. 21Bshows an example of the second MAC CE comprising four octets. A secondMAC CE (e.g., comprising four octets) may be associated with a thirdLCID. The third LCID may be different from the second LCID for thesecond MAC CE and/or the first LCID for activation/deactivation MAC CE.The second MAC CE (e.g., comprising one octet) may be used, for example,if there is no SCell with a serving cell index greater than a value(e.g., 7 or any other alue). The second MAC CE (e.g., comprising fouroctets) may be used, for example, if there is an SCell with a servingcell index greater than a value (e.g., 7 or any other value). A secondMAC CE may indicate a dormant/activated status of an SCell, for example,if a second MAC CE is received and a first MAC CE is not received. TheC_(i) field of the second MAC CE may indicate a dormant/activated statusof an SCell with SCell index i if there is an SCell configured withSCell index i, otherwise the wireless device (e.g., a MAC entity of thewireless device) may ignore the C_(i) field. A wireless device maytransition an SCell associated with SCell index i into dormant state,for example, if C_(i) of the second MAC CE is set to “1”. The wirelessdevice may activate an SCell associated with SCell index i, for example,if C_(i) of the second MAC CE is set to “0”. The wireless device mayactivate the SCell with SCell index i, for example, if C_(i) of thesecond MAC CE is set to “0” and the SCell with SCell index i is indormant state. The wireless device may ignore the C_(i) field of thesecond MAC CE, for example, if the C_(i) field is set to “0” and theSCell with SCell index i is not in dormant state.

FIG. 21C shows example configurations of a field of the first MAC CE.The field may comprise, for example, a C_(i) field of the first MAC CE(e.g., an activation/deactivation MAC CE), a C_(i) field of the secondMAC CE (e.g., a hibernation MAC CE), and corresponding resulting SCellstatus (e.g., activated/deactivated/dormant). The wireless device maydeactivate an SCell associated with SCell index i, for example, if C_(i)of hibernation MAC CE is set to 0, and C_(i) of theactivation/deactivation MAC CE is set to 0. The wireless device mayactivate an SCell associated with SCell index i, for example, if C_(i)of hibernation MAC CE is set to 0, and C_(i) of theactivation/deactivation MAC CE is set to 1. The wireless device mayignore the hibernation MAC CE and the activation/deactivation MAC CE,for example, if C_(i) of hibernation MAC CE is set to 1, and C_(i) ofthe activation/deactivation MAC CE is set to 0. The wireless device maytransition an SCell associated with SCell index I to a dormant state,for example, if C_(i) of hibernation MAC CE is set to 1, and C_(i) ofthe activation/deactivation MAC CE is set to 1.

FIG. 22 shows an example of SCell state transitions. The SCell statetransitions may be based on an activation/deactivation MAC CE and/or ahibernation MAC CE. A first MAC CE (e.g., activation/deactivation MACCE) and a second MAC CE (e.g., hibernation MAC CE) may indicate possiblestate transitions of the SCell with SCell index i if there is an SCellconfigured with SCell index i, and if both the first MAC CE and thesecond MAC CE are received, otherwise the wireless device (e.g., a MACentity of the wireless device) may ignore the C_(i) fields. The C_(i)fields of the two MAC CEs may be interpreted according to FIG. 21C. Afirst MAC CE (e.g., activation/deactivation MAC CE) or a second MAC CE(e.g., hibernation MAC CE) may indicate possible state transitions ofthe SCell with SCell index i, for example, if there is an SCellconfigured with SCell index i, and if one of the first MAC CE and thesecond MAC CE is received. A MAC entity of a wireless device may, forexample, deactivate an SCell, for example, if the MAC entity receives aMAC CE(s) (e.g., activation/deactivation MAC CE) indicating deactivationof an SCell. The MAC entity may, based on the MAC CE(s): deactivate theSCell, stop an SCell deactivation timer associated with the SCell,and/or flush all HARQ buffers associated with the SCell.

A base station may activate, hibernate, and/or deactivate at least oneof one or more SCells, for example, if the base station is configuredwith the one or more SCells. A MAC entity of a base station and/or awireless device may maintain an SCell deactivation timer (e.g.,sCellDeactivationTimer), for example, per a configured SCell and/orexcept for an SCell configured with PUCCH/SPUCCH, if any. The MAC entityof the base station and/or the wireless device may deactivate anassociated SCell, for example, if an SCell deactivation timer expires. AMAC entity of a base station and/or a wireless device may maintaindormant SCell deactivation timer (e.g., dormantSCellDeactivationTimer),for example, per a configured SCell and/or except for an SCellconfigured with PUCCH/SPUCCH, if any. The MAC entity of the base stationand/or the wireless device may deactivate an associated SCell, forexample, if the dormant SCell deactivation timer expires (e.g., if theSCell is in dormant state).

A MAC entity of a base station and/or a wireless device may, forexample, maintain an SCell hibernation timer (e.g.,sCellHibernationTimer), for example, per a configured SCell and/orexcept for an SCell configured with PUCCH/SPUCCH, if any. The MAC entityof the base station and/or the wireless device may hibernate anassociated SCell, for example, if the SCell hibernation timer expires(e.g., if the SCell is in active state). The SCell hibernation timer maytake priority over the SCell deactivation timer, for example, if boththe SCell deactivation timer and the SCell hibernation timer areconfigured. A base station and/or a wireless device may ignore the SCelldeactivation timer regardless of the SCell deactivation timer expiry,for example, if both the SCell deactivation timer and the SCellhibernation timer are configured.

FIG. 23 shows an example of SCell states (e.g., state transitions, stateswitching, etc.). The SCell state transitions may be based on, forexample, a first SCell timer (e.g., an SCell deactivation timer orsCellDeactivationTimer), a second SCell timer (e.g., an SCellhibernation timer or sCellHibernationTimer), and/or a third SCell timer(e.g., a dormant SCell deactivation timer ordormantSCellDeactivationTimer). A base station (e.g., a MAC entity of abase station) and/or a wireless device (e.g., a MAC entity of a wirelessdevice) may, for example, implement the SCell state transitions based onexpiration of the first SCell timer, the second SCell timer, and/or thethird SCell. The base station and/or the wireless device may, forexample, implement the SCell state transitions based on whether or not atimer (e.g., the second SCell timer) is configured. A base station(e.g., a MAC entity of a base station) and/or a wireless device (e.g., aMAC entity of a wireless device) may (e.g., if an SCell deactivationtimer expires and an SCell hibernation timer is not configured):deactivate an SCell, stop the SCell deactivation timer associated withthe SCell, and/or flush all HARQ buffers associated with the SCell.

A wireless device (e.g., MAC entity of a wireless device) may activatean SCell, for example, if the MAC entity is configured with an activatedSCell at SCell configuration. A wireless device (e.g., MAC entity of awireless device) may activate an SCell, for example, if the wirelessdevice receives a MAC CE(s) activating the SCell. The wireless device(e.g., MAC entity of a wireless device) maystart or restart an SCelldeactivation timer associated with an SCell, for example, based on or inresponse to activating the SCell. The wireless device (e.g., MAC entityof a wireless device) maystart or restart an SCell hibernation timer(e.g., if configured) associated with an SCell, for example, based on orin response to activating the SCell. A wireless device (e.g., MAC entityof a wireless device) may trigger a PHR procedure, for example, based onor in response to activating an SCell.

A wireless device (e.g., MAC entity of a wireless device) and/or a basestation (e.g., a MAC entity of a base station) may (e.g., if a firstPDCCH on an SCell indicates an uplink grant or downlink assignment, or asecond PDCCH on a serving cell scheduling the SCell indicates an uplinkgrant or a downlink assignment for the SCell, or a MAC PDU istransmitted in a configured uplink grant or received in a configureddownlink assignment) restart an SCell deactivation timer associated withan activated SCell and/or restart an SCell hibernation timer (e.g., ifconfigured) associated with the SCell. An ongoing random access (RA)procedure on an SCell may be aborted, for example, if, the SCell isdeactivated.

A wireless device (e.g., MAC entity of a wireless device) and/or a basestation (e.g., a MAC entity of a base station) may (e.g., if configuredwith an SCell associated with an SCell state set to dormant state uponthe SCell configuration, or if receiving MAC CE(s) for transitioning theSCell to dormant state): set (e.g., transition) the SCell to dormantstate, stop an SCell deactivation timer associated with the SCell, stopan SCell hibernation timer (e.g., if configured) associated with theSCell, start or restart a dormant SCell deactivation timer associatedwith the SCell, and/or flush all HARQ buffers associated with the SCell.The wireless device (e.g., MAC entity of a wireless device) and/or abase station (e.g., a MAC entity of a base station) may (e.g., if theSCell hibernation timer associated with the activated SCell expires):hibernate the SCell, stop the SCell deactivation timer associated withthe SCell, stop the SCell hibernation timer associated with the SCell,and/or flush all HARQ buffers associated with the SCell. The wirelessdevice (e.g., MAC entity of a wireless device) and/or a base station(e.g., a MAC entity of a base station) may (e.g., if a dormant SCelldeactivation timer associated with a dormant SCell expires): deactivatethe SCell and/or stop the dormant SCell deactivation timer associatedwith the SCell. Ongoing RA procedure on an SCell may be aborted, forexample, if the SCell is in dormant state.

A base station (e.g., a gNB) may configure a wireless device (e.g., aUE) with UL BWPs and DL BWPs to enable BA on a PCell. The base stationmay further configure the wireless device with at least DL BWP(s) (e.g.,there may be no UL BWPs in the UL) to enable BA on an SCell, if CA isconfigured. An initial active BWP may be a first BWP used for initialaccess, for example, for the PCell. A first active BWP may be a secondBWP configured for the wireless device to operate on the SCell, upon theSCell being activated. A base station and/or a wireless device mayindependently switch a DL BWP and an UL BWP, for example, if operatingin a paired spectrum (e.g., FDD). A base station and/or a wirelessdevice may simultaneously switch a DL BWP and an UL BWP, for example, ifoperating in an unpaired spectrum (e.g., TDD).

A base station and/or a wireless device may switch a BWP betweenconfigured BWPs, for example, based on a DCI or a BWP inactivity timer.A base station and/or a wireless device may switch an active BWP to adefault BWP, for example, based on or in response to an expiry of a BWPinactivity timer, if configured, associated with a serving cell. Thedefault BWP may be configured by the network.

One UL BWP for each uplink carrier and one DL BWP, for example, may beactive at a time in an active serving cell, for example, for FDD systemsthat are configured with BA. One DL/UL BWP pair, for example, may beactive at a time in an active serving cell, for example, for TDDsystems. Operating on the one UL BWP and the one DL BWP (or the oneDL/UL BWP pair) may, for example, improve wireless device batteryconsumption. BWPs other than the one active UL BWP and the one active DLBWP that the wireless device may work on may be deactivated. Ondeactivated BWPs, the wireless device may: not monitor PDCCH and/or nottransmit on a PUCCH, PRACH, and/or UL-SCH.

A serving cell may be configured with any number of BWPs (e.g., up tofour, or up to any other number of BWPs). There may be, for example, oneor any other number of active BWPs at any point in time for an activatedserving cell.

BWP switching for a serving cell may be used, for example, to activatean inactive BWP and/or deactivate an active BWP (e.g., at a time t). TheBWP switching may be controlled, for example, by a PDCCH indicating adownlink assignment and/or an uplink grant. The BWP switching may becontrolled, for example, by a BWP inactivity timer (e.g.,bwp-InactivityTimer). The BWP switching may be controlled, for example,by a MAC entity based on or in response to initiating an RA procedure.One or more BWPs may be initially active, without receiving a PDCCHindicating a downlink assignment or an uplink grant, for example, if anSpCell is added or an SCell is activated. The active BWP for a servingcell may be indicated by RRC message and/or PDCCH. A DL BWP may bepaired with an UL BWP, and BWP switching may be common for both UL andDL, for example, for unpaired spectrum.

A base station may configure a wireless device with one or moreTCI-States using and/or via higher layer signaling. A number (e.g.,quantity, plurality, etc.) of the one or more TCI-States may depend on acapability of the wireless device. The wireless device may use the oneor more TCI-States to decode a PDSCH based on a detected PDCCH. Each ofthe one or more TCI-States state may include one RS setTCI-RS-SetConfig. The one RS set TCI-RS-SetConfig may contain one ormore parameters. The one or more parameters may be used, for example, toconfigure quasi co-location relationship between one or more referencesignals in the RS set and the DM-RS port group of the PDSCH. The one RSset may contain a reference to either one or two DL RSs and anassociated quasi co-location type (QCL-Type) for each one as configuredby the higher layer parameter QCL-Type. QCL-Types associated with two DLRSs may not necessarily be the same, for example, if the one RS setcontains a reference to the two DL RSs. The references of the two DL RSsmay be, for example, to a same DL RS or to different DL RSs. TheQCL-Types indicated to the wireless device may be based on a higherlayer parameter QCL-Type. The higher layer parameter QCL-Type may takeone or a combination of the following types: QCL-TypeA′: {Doppler shift,Doppler spread, average delay, delay spread}, QCL-TypeB′: {Dopplershift, Doppler spread}, QCL-TypeC′: {average delay, Doppler shift} andQCL-TypeD′: {Spatial Rx parameter}.

A wireless device may receive an activation command. The activationcommand may be used to map one or more TCI states to one or morecodepoints of a TCI field in DCI. The wireless device may assume thatone or more antenna ports of one DM-RS port group of a PDSCH of aserving cell are spatially quasi co-located with an SSB, for example,(i) before the wireless device receives the activation command and/or(ii) after the wireless device receives a higher layer configuration ofTCI-States. The SSB may be determined in an initial access procedurewith respect to one or more of a Doppler shift, a Doppler spread, anaverage delay, a delay spread, and spatial Rx parameters, whereapplicable.

A wireless device may be configured by a base station, with a higherlayer parameter TCI-PresentInDCI. If the higher layer parameterTCI-PresentInDCI is set as ‘Enabled’ for a CORESET scheduling a PDSCH,the wireless device may assume that a TCI field is present in a DL DCIof a PDCCH transmitted on the CORESET. If the higher layer parameterTCI-PresentInDCI is set as ‘Disabled’ for a CORESET scheduling a PDSCHor if the PDSCH is scheduled by a DCI format 1_0 the wireless device mayassume, for determining PDSCH antenna port quasi co-location, that a TCIstate for the PDSCH is identical to the TCI state applied for theCORESET used for the PDCCH transmission.

The wireless device may use one or more TCI-States according to a valueof a TCI field in a detected PDCCH with DCI for determining PDSCHantenna port quasi co-location if the higher layer parameterTCI-PresentInDCI is set as ‘Enabled’. The wireless device may assumethat antenna ports of one DM-RS port group of a PDSCH of a serving cellare quasi co-located with one or more RS(s) in an RS set with respect toQCL type parameter(s) given by the indicated TCI state if a time offsetbetween the reception of the DL DCI and the corresponding PDSCH is equalto or greater than a threshold Threshold-Sched-Offset. The threshold maybe based on, for example, wireless device capability. The wirelessdevice may assume that antenna ports of one DM-RS port group of a PDSCHof a serving cell are quasi co-located based on a TCI state used forPDCCH quasi co-location indication of the lowest CORESET-ID in thelatest slot in which one or more CORESETs are configured for thewireless device, if (i) the offset between reception of the DL DCI andthe corresponding PDSCH is less than a threshold Threshold-Sched-Offsetand/or if (ii) the higher layer parameter TCI-PresentInDCI=‘Enabled’ orthe higher layer parameter TCI-PresentInDCI=‘Disabled’. The wirelessdevice may obtain the other QCL assumptions from the indicated TCIstates for its scheduled PDSCH, irrespective of a time offset betweenthe reception of the DL DCI and the corresponding PDSCH, if allconfigured TCI states do not contain QCL-TypeD′.

A base station and/or a wireless device may have multiple antennas, forexample, to support a transmission with high data rate (such as in an NRsystem). A wireless device may perform one or more beam managementprocedures, as shown in FIG. 9B, for example, if configured withmultiple antennas.

A wireless device may perform a downlink beam management based on one ormore CSI-RSs and/or one or more SS blocks. In a beam managementprocedure, a wireless device may measure a channel quality of a beampair link. The beam pair link may comprise a transmitting beam from abase station and a receiving beam at the wireless device. A wirelessdevice may measure the multiple beam pair links between the base stationand the wireless device, for example, if the wireless device isconfigured with multiple beams associated with multiple CSI-RSs and/orSS blocks.

A wireless device may send (e.g., transmit) one or more beam managementreports to a base station. The wireless device may indicate one or morebeam pair quality parameters, for example, in a beam management report.The one or more beam pair quality parameters may comprise at least oneor more beam identifications; RSRP; and/or PMI, CQI, and/or RI of atleast a subset of configured multiple beams.

A base station and/or a wireless device may perform a downlink beammanagement procedure on one or multiple Transmission and Receiving Point(TRPs), such as shown in FIG. 9B. Based on a wireless device's beammanagement report, a base station may send (e.g., transmit), to thewireless device, a signal indicating that a new beam pair link is aserving beam. The base station may transmit PDCCH and/or PDSCH to thewireless device using the serving beam.

A wireless device and/or a base station may trigger a beam failurerecovery mechanism. A wireless device may trigger a beam failurerecovery (BFR) procedure, for example, if at least a beam failureoccurs. A beam failure may occur if a quality of beam pair link(s) of atleast one PDCCH falls below a threshold. The threshold comprise be anRSRP value (e.g., −140 dbm, −110 dbm, or any other value) and/or a SINRvalue (e.g., −3 dB, −1 dB, or any other value), which may be configuredin a RRC message.

FIG. 24A shows an example of a first beam failure event. A base station2402 may send (e.g., transmit) a PDCCH from a transmission (Tx) beam toa receiving (Rx) beam of a wireless device 2401 from a TRP. The basestation 2402 and the wireless device 2401 may start a beam failurerecovery procedure on the TRP, for example, if the PDCCH on the beampair link (e.g., between the Tx beam of the base station 2402 and the Rxbeam of the wireless device 2401) have a lower-than-threshold RSRPand/or SINR value due to the beam pair link being blocked (e.g., by amoving vehicle 2403, a building, or any other obstruction).

FIG. 24B shows an example of a second beam failure event. A base stationmay send (e.g., transmit) a PDCCH from a beam to a wireless device 2411from a first TRP 2414. The base station and the wireless device 2411 maystart a beam failure recovery procedure on a new beam on a second TRP2412, for example, if the PDCCH on the beam is blocked (e.g., by amoving vehicle 2413, building, or any other obstruction).

A wireless device may measure a quality of beam pair links using one ormore RSs. The one or more RSs may comprise one or more SS blocks and/orone or more CSI-RS resources. A CSI-RS resource may be determined by aCSI-RS resource index (CRI). A quality of beam pair links may beindicated by, for example, an RSRP value, a reference signal receivedquality (e.g., RSRQ) value, and/or a CSI (e.g., SINR) value measured onRS resources. A base station may indicate whether an RS resource, usedfor measuring beam pair link quality, is QCLed (Quasi-Co-Located) withDM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH may beQCLed, for example, if the channel characteristics from a transmissionon an RS to a wireless device, and that from a transmission on a PDCCHto the wireless device, are similar or same under a configuredcriterion. The RS resource and the DM-RSs of the PDCCH may be QCLed, forexample, if Doppler shift and/or Doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are the same.

A wireless device may monitor a PDCCH on M beams (e.g. 2, 4, 8) pairlinks simultaneously, where M>1 and the value of M may depend at leaston capability of the wireless device. Monitoring a PDCCH may comprisedetecting DCI via the PDCCH transmitted on common search spaces and/orwireless device specific search spaces. Monitoring multiple beam pairlinks may increase robustness against beam pair link blocking. A basestation may send (e.g., transmit) one or more messages comprisingparameters indicating a wireless device to monitor PDCCH on differentbeam pair link(s) in different OFDM symbols.

A base station may send (e.g., transmit) one or more RRC messages and/orMAC CEs comprising parameters indicating Rx beam setting of a wirelessdevice for monitoring PDCCH on multiple beam pair links. A base stationmay send (e.g., transmit) an indication of a spatial QCL between DL RSantenna port(s) and DL RS antenna port(s) for demodulation of DL controlchannel. The indication may comprise a parameter in a MAC CE, an RRCmessage, DCI, and/or any combinations of these signaling.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of DL data channel, for example, forreception of data packet on a PDSCH. A base station may send (e.g.,transmit) DCI comprising parameters indicating the RS antenna port(s)are QCLed with DM-RS antenna port(s).

A wireless device may measure a beam pair link quality based on CSI-RSsQCLed with DM-RS for PDCCH, for example, if a base station sends (e.g.,transmits) a signal indicating QCL parameters between CSI-RS and DM-RSfor PDCCH. The wireless device may start a BFR procedure, for example,if multiple contiguous beam failures occur.

A wireless device may send (e.g., transmit) a BFR signal on an uplinkphysical channel to a base station, for example, if starting a BFRprocedure. The base station may send (e.g., transmit) DCI via a PDCCH ina CORESET, for example, after or in response to receiving the BFR signalon the uplink physical channel. The wireless may determine that the BFRprocedure is successfully completed, for example, after or in responseto receiving the DCI via the PDCCH in the CORESET.

A base station may send (e.g., transmit) one or more messages comprisingconfiguration parameters of an uplink physical channel, or signal, fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH(BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., BFR-PUCCH); and/or acontention-based PRACH resource (e.g., CF-PRACH). Combinations of thesecandidate signals and/or channels may be configured by the base station.A wireless device may autonomously select a first resource fortransmitting the BFR signal, for example, if the wireless device isconfigured with multiple resources for a BFR signal. The wireless devicemay select a BFR-PRACH resource for transmitting a BFR signal, forexample, if the wireless device is configured with the BFR-PRACHresource, a BFR-PUCCH resource, and/or a CF-PRACH resource. The basestation may send (e.g., transmit) a message to the wireless deviceindicating a resource for transmitting the BFR signal, for example, ifthe wireless device is configured with a BFR-PRACH resource, a BFR-PUCCHresource, and/or a CF-PRACH resource.

A base station may send (e.g., transmit) a response to a wirelessdevice, for example, after receiving one or more BFR signals. Theresponse may comprise the CRI associated with the candidate beam thatthe wireless device may indicate in the one or multiple BFR signals.

A base station and/or a wireless device may perform one or more beammanagement procedures, for example, if the base station and/or thewireless device are configured with multiple beams (e.g., in system suchas in an NR system). The wireless device may perform a BFR procedure(e.g., send one or more BFR signals), for example, if one or more beampair links between the base station and the wireless device fail.

A wireless device may receive one or more RRC messages that comprise BFRparameters. The one or more RRC messages may comprise one or more of anRRC connection reconfiguration message, an RRC connectionreestablishment message, and/or an RRC connection setup message. Thewireless device may detect at least one beam failure according to atleast one of BFR parameters and trigger a BFR procedure. The wirelessdevice may start a first timer, if configured, in response to detectingthe at least one beam failure. The wireless device may select a beam(e.g., a selected beam) in response to detecting the at least one beamfailure. The selected beam may be a beam with good channel quality(e.g., determined based on RSRP, SINR, or BLER, etc.) from a set ofcandidate beams. The set of candidate beams may be identified by a setof reference signals (e.g., SSBs, or CSI-RSs). The wireless device maytransmit at least a first BFR signal to a base station in response toselecting the selected beam. The at least first BFR signal may beassociated with the selected beam. The at least first BFR signal may be,for example, a preamble transmitted on a PRACH resource, or a beamfailure request (e.g., which may be similar to an SR) signal transmittedon a PUCCH resource, or a beam indication transmitted on a PUCCH/PUSCHresource. The wireless device may transmit the at least first BFR signalwith a transmission beam corresponding to a receiving beam associatedwith the selected beam. The wireless device, may, for example, determinetransmission beam by using the RF and/or digital beamforming parameterscorresponding to the receiving beam. The wireless device may start aresponse window in response to transmitting the at least first BFRsignal. The response window may be tracked using, for example, a timerwith a value configured by the base station. The wireless device maymonitor a PDCCH in a first CORESET while the response window is running.The first CORESET may be associated with the BFR procedure. The wirelessdevice may monitor the PDCCH in the first CORESET in condition oftransmitting the at least first BFR signal. The wireless device mayreceive a first DCI via the PDCCH in the first CORESET while theresponse window is running. The wireless device may consider the BFRprocedure successfully completed if the wireless device receives thefirst DCI via the PDCCH in the first CORESET before the response windowexpires. The wireless device may stop the first timer, if configured, ifthe BFR procedure is successfully completed.

FIG. 25 shows an example of a BFR procedure. In some communicationsystems, a wireless device may stop a BWP inactivity timer if a randomaccess procedure is initiated, and/or the wireless device may restartthe BWP inactivity timer if the random access procedure is successfullycompleted (e.g., based on or in response to receiving DCI addressed to aC-RNTI of the wireless device). At step 2500, a wireless device mayreceive one or more RRC messages comprising BFR parameters. At step2502, the wireless device may detect at least one beam failure accordingto at least one BFR parameter. The wireless device may start a firsttimer, if configured, based on detecting the at least one beam failure.At step 2504, the wireless device may select a beam (e.g., a selectedbeam) based on detecting the at least one beam failure. The selectedbeam may be a beam with good channel quality (e.g., based on RSRP, SINR,and/or BLER) that may be selected from a set of candidate beams. Thecandidate beams may be indicated by a set of reference signals (e.g.,SSBs, or CSI-RSs). At step 2506, the wireless device may send (e.g.,transmit) at least a first BFR signal to a base station, for example,based on selecting the beam (e.g., selected beam). The at least firstBFR signal may be associated with the selected beam. The wireless devicemay send (e.g., transmit) the at least first BFR signal with atransmission beam corresponding to a receiving beam associated with theselected beam. The at least first BFR signal may be a preamble sent(e.g., transmitted) via a PRACH resource, an SR signal sent (e.g.,transmitted) via a PUCCH resource, a beam failure recovery signal sent(e.g., transmitted) via a PUCCH resource, and/or a beam report sent(e.g., transmitted) via a PUCCH and/or PUSCH resource. At step 2508, thewireless device may start a response window, for example, based onsending (e.g., transmitting) the at least first BFR signal. The responsewindow may be associated with a timer with a value configured by thebase station. The wireless device may monitor a PDCCH in a firstCORESET, for example, if the response window is running. The firstCORESET may be configured by the BFR parameters (e.g., RRC). The firstCORESET may be associated with the BFR procedure. The wireless devicemay monitor the PDCCH in the first CORESET in condition of transmittingthe at least first BFR signal.

At step 2510, the wireless device may detect (e.g., receive) a first DCIvia the PDCCH in the first CORESET, for example, if the response windowis running. At step 2512, the wireless device may determine that the BFRprocedure has successfully completed, for example, if the wirelessdevice receives the first DCI via the PDCCH in the first CORESET beforethe response window expires. The wireless device may stop the firsttimer, if configured, based on the BFR procedure successfully beingcompleted. The wireless device may stop the response window, forexample, based on the BFR procedure successfully being completed. If theresponse window expires, and the wireless device does not receive theDCI (e.g., at step 2510), the wireless device may, at step 2514,increment a transmission number. The transmission number may beinitialized to a first number (e.g., 0) before the BFR procedure istriggered. At step 2514, if the transmission number indicates a numberless than the configured maximum transmission number, the wirelessdevice may repeat one or more actions (e.g., at step 2504). The one ormore actions to be repeated may comprise at least one of a BFR signaltransmission, starting the response window, monitoring the PDCCH, and/orincrementing the transmission number, for example, if no responsereceived during the response window is running. At step 2516, if thetransmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed.

A MAC entity of a wireless device may be configured by an RRC message,for example, for a beam failure recovery procedure. The beam failurerecovery procedure may be used for indicating to a serving base stationof a new (e.g., candidate) synchronization signal block (SSB) and/orCSI-RS, for example, if a beam failure is detected. The beam failure maybe detected on one or more serving SSB(s) and/or CSI-RS(s) of theserving base station. The beam failure may be detected by counting abeam failure instance indication from a lower layer of the wirelessdevice (e.g., PHY layer) to the MAC entity.

An RRC message may configure a wireless device with one or moreparameters (e.g., in BeamFailureRecoveryConfig) for a beam failuredetection and recovery procedure. The one or more parameters maycomprise one or more of: beamFailureInstanceMaxCount for a beam failuredetection, beamFailureDetectionTimer for the beam failure detection,beamFailureRecoveryTimer for a beam failure recovery procedure,rsrp-ThresholdSSB, an RSRP threshold for a beam failure recovery,PowerRampingStep for the beam failure recovery,preambleReceivedTargetPower for the beam failure recovery, preambleTxMaxfor the beam failure recovery, and/or ra-ResponseWindow. Thera-ResponseWindow may be a time window to monitor one or more responsesfor the beam failure recovery using a contention-free RA preamble.

FIG. 26 shows an example of beam failure instance (BFI) indication. Awireless device may use at least one wireless device variable for a beamfailure detection. A BFI counter (e.g., BFI_COUNTER) may be one of theat least one wireless device variable. The BFI counter may be a counterfor a beam failure instance indication. The BFI counter may be initiallyset to zero before time T 2600. The wireless device may start or restarta beam failure detection timer (e.g., beamFailureDetectionTimer) at timeT 2600 and increment the BFI counter, for example, based on a MAC entityof a wireless device receiving a beam failure instance indication from alower layer (e.g., PHY) of the wireless device. The wireless device mayincrement the BFI counter, for example, in addition to starting orrestarting the beam failure detection timer (e.g., BFR timer in FIG. 26at time T 2600, 2T 2602, 4T 2606, 5T 2608, 6T 2610, etc.). The wirelessdevice may initiate a random access procedure such as for a beam failurerecovery (e.g., on an SpCell, and/or if configured withBeamFailureRecoveryConfig) based on the BFI counter being greater thanor equal to a value such as beamFailureInstanceMaxCount (e.g., at time T2600, 2T 2602, 5T 2608 in FIG. 26). The wireless device may start a beamfailure recovery timer (e.g., beamFailureRecoveryTimer, if configured),for example, based on the wireless device being configured with a beamfailure recovery configuration (e.g., BeamFailureRecoveryConfig). Thewireless device may start the beam failure recovery timer, for example,based on or in response to a BFI counter (e.g., BFI_COUNTER) being equalto or greater than a value such as beamFailureInstanceMaxCount. Thewireless device may use the one or more parameters in the beam failurerecover configuration (e.g., powerRampingStep,preambleReceivedTargetPower, and/or preambleTransMax), for example,based on or in response to the initiating the random access procedure.The wireless device may set the BFI counter to zero, for example, basedon the beam failure detection timer expiring. The wireless device maydetermine that the beam failure recovery procedure has successfullycompleted, for example, based on the random access procedure beingsuccessfully completed. The random access procedure may be acontention-free random access procedure.

A wireless device may initiate a random access procedure (e.g., on anSpCell) for a beam failure recovery, for example, based on or inresponse to a BFI counter (e.g., BFI_COUNTER) being greater than orequal to a value such as beamFailureInstanceMaxCount. The random accessprocedure may be a contention-based random access procedure.

A wireless device may initiate a random access procedure at time 6T2610, for example, a based on a first number (e.g., 3) is reached. Thewireless device may set the BFI counter to zero (e.g., in FIG. 26,between time 3T 2604 and 4T 2606), for example, based on the beamfailure detection timer expiring. The wireless device may determine thatthe beam failure recovery procedure has successfully completed, forexample, based on the random access procedure (e.g., a contention-freerandom access or a contention-based random access) being successfullycompleted. The wireless device may stop the beam failure recovery timer(if configured), for example, based on the random access procedure(e.g., a contention-free random access) is successfully completed.

A wireless device (e.g., a MAC entity of the wireless device) may startra-ResponseWindow at a first PDCCH occasion from the end of thetransmitting the contention-free random access preamble, for example, ifa MAC entity of a wireless device sends (e.g., transmits) acontention-free random access preamble for a BFR procedure. Thera-ResponseWindow may be configured in BeamFailureRecoveryConfig. Thewireless device may monitor at least one PDCCH (e.g., of an SpCell) fora response to the beam failure recovery request, for example, if thera-ResponseWindow is running. The beam failure recovery request may beidentified by a C-RNTI. The wireless device may determine that a randomaccess procedure has successfully completed, for example, if a MACentity of a wireless device receives, from a lower layer of the wirelessdevice, a notification of a reception of at least one PDCCHtransmission, and if the at least one PDCCH transmission is addressed toa C-RNTI, and/or if a contention-free random access preamble for a beamfailure recovery request is transmitted by the MAC entity.

A wireless device may initiate a contention-based random access preamblefor a beam failure recovery request. A MAC entity of the wireless devicemay start ra-ContentionResolutionTimer, for example, if the wirelessdevice transmits Msg3. The ra-ContentionResolutionTimer may beconfigured by RRC. Based on the starting thera-ContentionResolutionTimer, the wireless device may monitor at leastone PDCCH if the ra-ContentionResolutionTimer is running. The wirelessdevice may consider the random access procedure successfully completed,for example, if the MAC entity receives, from a lower layer of thewireless device, a notification of a reception of the at least one PDCCHtransmission, if a C-RNTI MAC CE is included in the Msg3, if a randomaccess procedure is initiated for a beam failure recovery, and/or the atleast one PDCCH transmission is addressed to a C-RNTI of the wirelessdevice. The wireless device may stop the ra-ContentionResolutionTimer,for example, based on the random access procedure being successfullycompleted. The wireless device may determine that the beam failurerecovery has successfully completed, for example, if a random accessprocedure of a beam failure recovery is successfully completed.

A wireless device may be configured (e.g., for a serving cell) with afirst set of periodic CSI-RS resource configuration indexes by a higherlayer parameter (e.g., Beam-Failure-Detection-RS-ResourceConfig,failureDetectionResources, etc.). The wireless device may be configuredwith a second set of CSI-RS resource configuration indexes and/orSS/PBCH block indexes by a higher layer parameter (e.g.,Candidate-Beam-RS-List, candidateBeamRSList, etc.). The first set ofCSI-RS resource configuration indexes and/or SS/PBCH block indexesand/or the second set of CSI-RS resource configuration indexes and/orSS/PBCH block indexes may be used for radio link quality measurements onthe serving cell. The wireless device may determine a first set toinclude SS/PBCH block indexes and periodic CSI-RS resource configurationindexes, for example, if a wireless device is not provided with higherlayer parameter Beam-Failure-Detection-RS-ResourceConfig. The SS/PBCHblock indexes and the periodic CSI-RS resource configuration indexes maycomprise the same values as one or more RS indexes in one or more RSsets. The one or more RS indexes in the one or more RS sets may beindicated by one or more TCI states. The one or more TCI states may beused for respective control resource sets for which the wireless devicemay be configured to monitor a PDCCH. The wireless device may expect asingle port RS in the first set.

A wireless device may expect a first set of periodic CSI-RS resourceconfigurations to include, for example, up to two RS indexes. The firstset of periodic CSI-RS resource configurations may include one or moreRS indexes with QCL-TypeD configuration, for example, based on the firstset of periodic CSI-RS resource configurations includes two RS indexes.A wireless device may expect a single port RS in the first set ofperiodic CSI-RS resource configurations.

A first threshold (e.g., Qout,LR) may correspond to a first defaultvalue of a first higher layer parameter (e.g.,RLM-IS-OOS-thresholdConfig, rlmInSyncOutOfSyncThreshold, etc.). A secondthreshold (e.g., Qin,LR) may correspond to a second default value of ahigher layer parameter (e.g., Beam-failure-candidate-beam-threshold,rsrp-ThresholdSSB, etc.). A physical layer in the wireless device maycompare a first radio link quality according to the first set ofperiodic CSI-RS resource configurations with the first threshold. Forthe first set, the wireless device may assess the first radio linkquality based on periodic CSI-RS resource configurations or SS/PBCHblocks. The periodic CSI-RS resource configurations and/or the SS/PBCHblocks may be associated (e.g., quasi co-located) with at least oneDM-RS of a PDCCH that may be monitored by the wireless device. Thewireless device may apply the second threshold to a first L1-RSRPmeasurement that may be obtained from one or more SS/PBCH blocks. Thewireless device may apply the second threshold to a second L1-RSRPmeasurement that may be obtained from one or more periodic CSI-RSresources, for example after scaling a respective CSI-RS reception powerwith a value provided by a higher layer parameter (e.g., Pc_SS,powerControlOffsetSS, etc.).

A wireless device may assess the first radio link quality of the firstset. A physical layer in the wireless device may provide an indicationto higher layers (e.g., MAC), for example, if the first radio linkquality for all corresponding resource configurations in the first setis less than the first threshold. The wireless device may use thecorresponding resource configurations in the first set to assess thefirst radio link quality. The physical layer may inform the higherlayers (e.g., MAC, RRC), for example, if the first radio link quality isless than the first threshold with a first periodicity. The firstperiodicity may be determined by the maximum of the shortest periodicityof periodic CSI-RS configurations or SS/PBCH blocks in the first set anda time value (e.g., 2 ms or any other duration). The wireless device mayaccess the periodic CSI-RS configurations or the SS/PBCH blocks for thefirst radio link quality. Based on a request from higher layers (e.g.,MAC layer), a wireless device may provide to higher layers the periodicCSI-RS configuration indexes and/or the SS/PBCH block indexes from thesecond set. The wireless device may provide, to higher layers,corresponding L1-RSRP measurements that may be greater than or equal tothe second threshold.

A wireless device may be configured with one CORESET, for example, by ahigher layer parameter (e.g., Beam-failure-Recovery-Response-CORESET)and/or via a link to a search space set. The wireless device may beconfigured with an associated search space that may be provided by ahigher layer parameter (e.g., search-space-config,recoverySearchSpaceId, etc.). The search space may be used formonitoring a PDCCH in the control resource set. The wireless device maynot expect to be provided with a second search space set for monitoringthe CORESET, for example, if the wireless device is provided by a higherlayer parameter (e.g., recoverySearchSpaceId). The CORESET may beassociated with the search space set provided by a higher layerparameter (e.g., recoverySearchSpaceId). The wireless device may receivefrom higher layers (e.g., MAC layer), by a parameter (e.g.,PRACH-ResourceDedicatedBFR), a configuration for a PRACH transmission.For the PRACH transmission in slot n and based on antenna port quasico-location parameters associated with periodic CSI-RS configuration orSS/PBCH block with a first RS index, the wireless device may monitor thePDCCH in a search space set (e.g., which may be provided by a higherlayer parameter such as recoverySearchSpaceId) for detection of a DCIformat starting from a slot (e.g., slot n+4) within a window. The windowmay be configured by a higher layer parameter (e.g.,Beam-failure-recovery-request-window, BeamFailureRecoveryConfig, etc.).The DCI format may be CRC scrambled by a C-RNTI. The first RS index maybe provided by the higher layers. For a PDCCH monitoring and for acorresponding PDSCH reception, the wireless device may use the sameantenna port quasi-collocation parameters with the first RS index (e.g.,as for monitoring the PDCCH) until the wireless device receives, byhigher layers, an activation for a TCI state or a parameter (e.g.,TCI-StatesPDCCH, ToAddlist, TCI-StatesPDCCH-ToReleaseList).

A wireless device may monitor PDCCH candidates in a search space set.The wireless device may monitor the PDCCH candidates in the search spaceset, for example, at least until the wireless device receives a MAC CEactivation command for a TCI state or a higher layer parameter (e.g.,TCI-StatesPDCCH-ToAddlist and/or TCI-StatesPDCCH-ToReleaseList), forexample, after the wireless device detects the DCI format with CRCscrambled by the C-RNTI in the search space set (e.g., which may be bythe higher layer parameter recoverySearchSpaceId). The wireless devicemay not expect to receive a PDCCH order triggering a PRACH transmission,for example, based on the wireless device not being provided with acoreset for a search space set (e.g., provided by a higher layerparameter recoverySearchSpaceId). The wireless device may initiate acontention-based random access procedure for a beam failure recovery,for example, based on or in response to not being provided with thecoreset. The wireless device may not expect to receive a PDCCH ordertriggering a PRACH transmission, for example, based on the wirelessdevice not being provided with a higher layer parameter (e.g.,recoverySearchSpaceId). A wireless device may initiate acontention-based random access procedure for a beam failure recovery,for example, based on or in response to not being provided with thehigher layer parameter (e.g., recoverySearchSpaceId).

A base station may configure a wireless device with uplink (UL)bandwidth parts (BWPs) and downlink (DL) BWPs, for example, to enablebandwidth adaptation (BA) for a PCell. The base station may configurethe wireless device with at least DL BWP(s) (e.g., an SCell may not haveUL BWPS) to enable BA for an SCell, for example, if CA is configured.For the PCell, a first initial BWP may be a first BWP used for initialaccess. For the SCell, a second initial BWP may be a second BWPconfigured for the wireless device to first operate on the SCell if theSCell is activated.

A wireless device may switch a first (e.g., active) DL BWP and a first(e.g., active) UL BWP independently, for example, in paired spectrum(e.g., FDD). A wireless device may switch a second (e.g., active) DL BWPand a second (e.g., active) UL BWP simultaneously, for example, inunpaired spectrum (e.g., TDD). Switching between configured BWPs may bebased on DCI and/or an inactivity timer. An expiry of the inactivitytimer associated with a cell may switch an active BWP to a default BWP,for example, if the inactivity timer is configured for a serving cell.The default BWP may be configured by the network.

One UL BWP for each uplink carrier and one DL BWP may be active at atime in an active serving cell, for example, in FDD systems configuredwith BA. One DL/UL BWP pair may be active at a time in an active servingcell, for example, in TDD systems. Operating on the one UL BWP and theone DL BWP (and/or the one DL/UL pair) may enable a wireless device touse a reasonable amount of power (e.g., reasonable battery consumption).BWPs other than the one UL BWP and the one DL BWP that the wirelessdevice may be configured with may be deactivated. The wireless devicemay refrain from monitoring a PDCCH, and/or may refrain fromtransmitting via a PUCCH, PRACH and/or UL-SCH, for example, ondeactivated BWPs.

A serving cell may be configured with a first number (e.g., four) ofBWPs. A wireless device and/or a base station may have one active BWP atany point in time, for example, for an activated serving cell (e.g.,PCell, SCell). A BWP switching for a serving cell may be used toactivate an inactive BWP and/or deactivate an active BWP. The BWPswitching may be controlled by a PDCCH indicating a downlink assignmentor an uplink grant. The BWP switching may be controlled by an inactivitytimer (e.g., bwpInactivityTimer). The BWP switching may be controlled byan RRC signaling. The BWP switching may be controlled by a MAC entity,for example, based on initiating a random access procedure. A DL BWP(e.g., indicated by first ActiveDownlinkBWP-ID which may be included inRRC signaling) and/or an UL BWP (e.g., indicated byfirstActiveDuplinkBWP-ID which may be included in RRC signaling) may beinitially active without receiving a PDCCH indicating a downlinkassignment or an uplink grant, for example, based on an addition of anSpCell or an activation of an SCell. The active BWP for a serving cellmay be indicated by an RRC message and/or a PDCCH message (e.g., PDCCHorder). A DL BWP may be paired with an UL BWP, and/or BWP switching maybe common for both UL and DL, for example, for unpaired spectrum (e.g.,TDD).

A MAC entity, for an activated serving cell (e.g., PCell, SCell)configured with one or more BWPs and/or based on the BWP beingactivated, may perform at least one of: transmitting via an UL-SCH usingthe one or more BWPs; transmitting via a RACH using the one or moreBWPs; monitoring a PDCCH using the one or more BWPs; transmitting an SRSusing the one or more BWPs; transmitting via a PUCCH using the one ormore BWPs; receiving via a DL-SCH using the one or more BWPs;initializing or reinitializing any suspended configured uplink grants ofconfigured grant Type 1 using the one or more BWPs (e.g., based on astored configuration, if any); and/or to start in a symbol (e.g., basedon a procedure).

A wireless device (e.g., a MAC entity of a wireless device), for anactivated serving cell (e.g., PCell, SCell) configured with one or moreBWPs and/or based on the BWP being deactivated, may not transmit via aUL-SCH using the one or more BWPs; may not transmit via a RACH using theone or more BWPs; may not monitor a PDCCH using the one or more BWPs;may not report CSI for the one or more BWPs; may not transmit via aPUCCH using the one or more BWPs; may not transmit an SRS using the oneor more BWPs, may not receive via a DL-SCH using the one or more BWPs;may clear any configured downlink assignment and configured uplink grantof configured grant Type 2 using the one or more BWPs; and/or maysuspend any configured uplink grant of configured Type 1 using the oneor more BWPs (e.g., inactive BWPs).

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedure(e.g., contention-based random access, contention-free random access) ona serving cell, for example, based on PRACH occasions being configuredfor an active UL BWP, of the serving cell, with an uplink BWP ID; theserving cell being an SpCell; and/or a downlink BWP ID of an active DLBWP of the serving cell not being the same as the uplink BWP ID. Thebase station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may switch from the active DL BWP to aDL BWP with a second downlink BWP ID same as the uplink BWP ID, forexample, based on the prior initiation. The base station and/or awireless device (e.g., a MAC entity of a base station and/or a wirelessdevice) may perform the random access procedure on the DL BWP of theserving cell (e.g., SpCell) and the active UL BWP of the serving cell,for example, based on or in response to the switching.

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedure(e.g., contention-based random access, contention-free random access) ona serving cell (e.g., SCell), for example, based on PRACH occasionsbeing configured for an active UL BWP of the serving cell; and/or theserving cell not being an SpCell. The base station and/or a wirelessdevice (e.g., a MAC entity of a base station and/or a wireless device)may perform the random access procedure on an active DL BWP of an SpCelland an active UL BWP of the serving cell, for example, based on theinitiation.

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedureon a serving cell, for example, based on PRACH resources not beingconfigured for an active UL BWP of the serving cell. The MAC entity mayswitch the active UL BWP to an uplink BWP (initial uplink BWP), forexample, based on the initiation. The uplink BWP may be indicated by RRCsignaling (e.g., initialULBWP). The base station and/or a wirelessdevice (e.g., a MAC entity of a base station and/or a wireless device)may switch an active DL BWP to a downlink BWP (e.g., initial downlinkBWP), for example, based on the serving cell being an SpCell. Thedownlink BWP may be indicated by RRC signaling (e.g., initialDLBWP). Thebase station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may perform the random accessprocedure on the uplink BWP and the downlink BWP, for example, based onor in response to the switching.

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedureon a serving cell, for example, based on PRACH resources not beingconfigured for an active UL BWP of the serving cell (e.g., SCell). Thebase station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may switch the active UL BWP to anuplink BWP (initial uplink BWP), for example, based on the initiation.The uplink BWP may be indicated by RRC signaling (e.g., initialULBWP).The base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may perform the random accessprocedure on the uplink BWP and an active downlink BWP of an SpCell, forexample, based on the serving cell is not an SpCell.

A wireless device may perform BWP switching to a BWP indicated by aPDCCH, for example, if a base station and/or a wireless device (e.g., aMAC entity of a base station and/or a wireless device) receives a PDCCH(e.g., a PDCCH order) for a BWP switching for a serving cell, forexample, if a random access procedure associated with this serving cellis not ongoing. A wireless device may determine whether to switch a BWPor ignore the PDCCH for the BWP switching, for example, if a basestation and/or a wireless device (e.g., a MAC entity of a base stationand/or a wireless device) received a PDCCH for a BWP switching for aserving cell while a random access procedure is ongoing in the MACentity. The wireless device may perform the BWP switching to a new BWPindicated by the PDCCH. The base station and/or a wireless device (e.g.,a MAC entity of a base station and/or a wireless device) may stop theongoing random access procedure and initiate a second random accessprocedure on a new BWP, for example, if the MAC entity decides toperform BWP switching to the new BWP (e.g., which may be indicated bythe PDCCH), for example, based on or in response to receiving a PDCCH(e.g., other than successful contention resolution). The base stationand/or a wireless device (e.g., a MAC entity of a base station and/or awireless device) may continue with the ongoing random access procedureon an active BWP, for example if the MAC decides to ignore the PDCCH forthe BWP switching.

The base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may start or restart a BWP inactivitytimer associated with the active DL BWP for a variety of reasons. TheMAC entity may start or restart a BWP inactivity timer (e.g.,BWP-InactivityTimer) associated with the active DL BWP, for example, ifone or more of the following occur: a BWP inactivity timer is configured(e.g., via RRC signaling including defaultDownlinkBWP parameter) for anactivated serving sell, if a Default-DL-BWP is configured and an activeDL BWP is not a BWP indicated by the Default-DL-BWP, if theDefault-DL-BWP is not configured and the active DL BWP is not theinitial DL BWP (e.g., via RRC signaling includinginitialDownlinkBWPparameter); and/or if one or more of the followingoccur: if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlinkassignment or uplink grant is received on or for the active BWP, and/orif there is not an ongoing random access procedure associated with theactivated serving cell.

The base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may start or restart the BWPinactivity timer (e.g., BWP-InactivityTimer) associated with the activeDL BWP, for example, if one or more of the following occur: if aBWP-InactivityTimer is configured for an activated serving cell, if aDefault-DL-BWP is configured and an active DL BWP is not a BWP indicatedby the Default-DL-BWP, and/or if the Default-DL-BWP is not configuredand an active DL BWP is not the initial DL BWP; and/or if one or more ofthe following occur: if a MAC-PDU is transmitted in a configured uplinkgrant or received in a configured downlink assignment, and/or if thereis not an ongoing random access procedure associated with the activatedserving cell.

The base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may start or restart the BWPinactivity timer (e.g., BWP-InactivityTimer) associated with the activeDL BWP, for example, if one or more of the following occur: if aBWP-InactivityTimer is configured for an activated serving cell, if aDefault-DL-BWP is configured and an active DL BWP is not a BWP indicatedby the Default-DL-BWP, and/or if the Default-DL-BWP is not configuredand the active DL BWP is not the initial DL BWP; and/or if one or moreof the following occur: if a PDCCH addressed to C-RNTI or CS-RNTIindicating downlink assignment or uplink grant is received on or for theactive BWP, if a MAC-PDU is transmitted in a configured uplink grant orreceived in a configured downlink assignment, and/or if an ongoingrandom access procedure associated with the activated Serving Cell issuccessfully completed in response to receiving a PDCCH addressed to aC-RNTI.

The base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may start or restart the BWPinactivity timer (e.g., BWP-InactivityTimer) associated with the activeDL BWP based on switching the active BWP. For example, the MAC entitymay start or restart the BWP-InactivityTimer associated with the activeDL BWP if a PDCCH for BWP switching is received and the wireless deviceswitches an active DL BWP to the DL BWP, and/or if one or more of thefollowing occur: if a default downlink BWP is configured and the DL BWPis not the default downlink BWP, and/or if a default downlink BWP is notconfigured and the DL BWP is not the initial downlink BWP.

The base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may stop the BWP inactivity timer(e.g., BWP-InactivityTimer) associated with an active DL BWP of theactivated serving cell, for example, if one or more of the followingoccur: if BWP-InactivityTimer is configured for an activated servingcell, if the Default-DL-BWP is configured and the active DL BWP is notthe BWP indicated by the Default-DL-BWP, and/or if the Default-DL-BWP isnot configured and the active DL BWP is not the initial BWP; and/or if arandom access procedure is initiated on the activated serving cell. TheMAC entity may stop a second BWP inactivity timer (e.g.,BWP-InactivityTimer) associated with a second active DL BWP of anSpCell, for example, if the activated Serving Cell is an SCell (otherthan a PSCell).

The base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may perform BWP switching to a BWPindicated by the Default-DL-BWP, for example, if one or more of thefollowing occur: if a BWP inactivity timer (e.g., BWP-InactivityTimer)is configured for an activated serving cell, if the Default-DL-BWP isconfigured and the active DL BWP is not the BWP indicated by theDefault-DL-BWP, if the Default-DL-BWP is not configured and the activeDL BWP is not the initial BWP, if BWP-InactivityTimer associated withthe active DL BWP expires, and/or if the Default-DL-BWP is configured.The MAC entity may perform BWP switching to the initial DL BWP, forexample, if the MAC entity may refrain from performing BWP switching toa BWP indicated by the Default-DL-BWP.

A wireless device may be configured for operation in BWPs of a servingcell. The wireless device may be configured by higher layers for theserving cell for a set of (e.g., four) bandwidth parts (BWPs) forreceptions by the wireless device (e.g., DL BWP set) in a DL bandwidthby a parameter (e.g., DL-BWP). The wireless device may be configuredwith a set of (e.g., four) BWPs for transmissions by the wireless device(e.g., UL BWP set) in an UL bandwidth by a parameter (e.g., UL-BWP) forthe serving cell. An initial active DL BWP may be determined, forexample, by: a location and number of contiguous PRBs; a subcarrierspacing; and/or a cyclic prefix (e.g., for the control resource set fora Type0-PDCCH common search space). A wireless device may be provided(e.g., by a higher layer) a parameter (e.g., initial-UL-BWP) for aninitial active UL BWP for a random access procedure, for example, foroperation on a primary cell or on a secondary cell. The wireless devicemay be provided with an initial active UL BWP (e.g., by a higher layer)parameter (e.g., Active-BWP-DL-PCell, initialuplinkBWP, etc.) for firstactive DL BWP for receptions, for example, if a wireless device has adedicated BWP configuration. The wireless device may be provided with aninitial uplink BWP on a supplementary carrier by a second higher layerparameter (e.g., initialUplinkBWP in a supplementary uplink), forexample, if the wireless device is configured with a supplementarycarrier. The wireless device may be provided (e.g., by a higher layer) aparameter (e.g., Active-BWP-UL-PCell, firstActiveDownlinkBWP-Id, etc.)for a first active UL BWP for transmissions on a primary cell, forexample, if a wireless device has a dedicated BWP configuration. Thehigher layer parameter may indicate a first active DL BWP forreceptions. The wireless device may be provided by a second higher layerparameter (e.g., firstActiveUplinkBWP-Id), for example, if the wirelessdevice has a dedicated BWP configuration. The higher layer parameter mayindicate a first active UL BWP for transmissions on the primary cell.

In an example, for a DL BWP or an UL BWP in a first set of DL BWPs or asecond set of UL BWPs, respectively, the UE may be configured with atleast one of the following parameters for a serving cell: a subcarrierspacing provided by higher layer parameter subcarrierSpacing orUL-BWP-mu; a cyclic prefix provided by higher layer parametercyclicPrefix; an index in the first set of DL BWPs or in the second setof UL BWPs by respective higher layer parameters bwp-Id (e.g.,DL-BWP-ID, UL-BWP-ID); a third set of BWP-common and a fourth set ofBWP-dedicated parameters by a higher layer parameter bwp-Common and ahigher layer parameter bwp-Dedicated, respectively.

A DL BWP from a first set of configured DL BWPs (e.g., with a DL BWPindex provided by higher layer parameter such as bwp-ID for the DL BWP)may be paired and/or linked with an UL BWP from a second set ofconfigured UL BWPs (e.g., with an UL BWP index provided by higher layerparameter such as bwp-ID for the UL BWP). A DL BWP from a first set ofconfigured DL BWPs may be paired with an UL BWP from a first set ofconfigured UL BWPs, for example, if the DL BWP index and the UL BWPindex are equal (e.g., for unpaired spectrum operation). A wirelessdevice may not expect to receive a configuration where the centerfrequency for a DL BWP is different from the center frequency for an ULBWP, for example, if the DL-BWP-index of the DL BWP is equal to theUL-BWP-index of the UL BWP (e.g., for unpaired spectrum operation).

A wireless device may be configured with CORESETs for every type ofcommon search space and/or for wireless device-specific search space,for example, for a DL BWP in a first set of DL BWPs on a primary cell.The wireless device may not expect to be configured without a commonsearch space on the PCell, or on the PSCell, in the DL BWP (e.g., activeDL BWP). The wireless device may be configured with control resourcesets for PUCCH transmissions, for example, for an UL BWP in a second setof UL BWPs. A wireless device may receive a PDCCH message and/or a PDSCHmessage in a DL BWP, for example, according to a configured subcarrierspacing and/or a CP length for the DL BWP. A wireless device maytransmit via a PUCCH and/or via a PUSCH in an UL BWP, for example,according to a configured subcarrier spacing and CP length for the ULBWP.

A BWP indicator field value may indicate an active DL BWP, from thefirst set of configured DL BWPs, for DL receptions, for example, if theBWP indicator field is configured in DCI format 1_1. The BWP indicatorfield value may indicate an active UL BWP, from the second set ofconfigured UL BWPs, for UL transmissions.

The wireless device may set the active UL BWP to the UL BWP indicated bythe bandwidth part indicator field in the DCI format 0_1, for example,based on a bandwidth part indicator field being configured in DCI format0_1 and/or the bandwidth part indicator field value indicating an UL BWPdifferent from an active UL BWP. The wireless device may set the activeDL BWP to the DL BWP indicated by the bandwidth part indicator field inthe DCI format 1_1, for example, based on a bandwidth part indicatorfield being configured in DCI format 1_1 and/or the bandwidth partindicator field value indicating a DL BWP different from an active DLBWP.

A wireless device may be provided (e.g., for the primary cell) with ahigher layer parameter (e.g., Default-DL-BWP, defaultDownlinkBWP-Id, orany other a default DL BWP among the configured DL BWPs), for example,if a BWP indicator field is configured in DCI format 0_1. The higherlayer parameter may indicate a default DL BWP among configured DL BWPs.The default BWP may be the initial active DL BWP, for example, if awireless device is not provided a default DL BWP by a higher layerparameter (e.g., Default-DL-BWP, defaultDownlinkBWP-Id, etc.). Awireless device may detect a DCI format 0_1 indicating active UL BWPchange, or a DCI format 1_1 indicating active DL BWP change, forexample, if a corresponding PDCCH is received within first three symbolsof a slot.

The wireless device procedures on the secondary cell may be same as on aprimary cell. The wireless device procedures on the secondary cell maybe the same as on a primary cell, for example, based on the wirelessdevice being configured for a secondary cell with higher layer parameter(e.g., defaultDownlinkBWP-Id) indicating a default DL BWP among theconfigured DL BWPs and/or the wireless device being configured withhigher layer parameter bwp-inactivitytimer indicating a timer value. Anoperation of the timer value for the secondary cell and the default DLBWP for the secondary cell may be similar to or the same as operationsusing a timer value for the primary cell and a default DL BWP for theprimary cell.

A wireless device may be provided by a higher layer parameter (e.g.,BWP-InactivityTimer).

The higher layer parameter may indicate a timer with a timer value for aserving cell (e.g., primary cell, secondary cell). The wireless devicemay increment the timer every interval (e.g., every interval of 1millisecond for frequency range 1, every 0.5 milliseconds for frequencyrange 2, or any other interval for any other frequency range), forexample, based on the timer being configured, the timer running, and/orthe wireless device not detecting a DCI format for PDSCH reception onthe serving cell for paired spectrum operation. The wireless device maydecrement the timer every interval (e.g., every interval of 1millisecond for frequency range 1, every 0.5 milliseconds for frequencyrange 2, or any other interval for any other frequency range), forexample, based on the timer being configured, the timer running, thewireless device not detecting a first DCI format for PDSCH receptionand/or the wireless device not detecting a second DCI format for PUSCHtransmission on the serving cell for unpaired spectrum operation duringthe interval.

A wireless device may be configured by a higher layer (e.g., theconfiguration including parameter firstActiveDownlinkBWP-Id and/orparameter firstActiveUplinkBWP-Id). The higher layer parameter (e.g.,firstActiveDownlinkBWP-Id) may indicate a first active DL BWP on aserving cell (e.g., secondary cell) and/or on a supplementary carrier.The wireless device may use the first active DL BWP on the serving cellas the respective first active DL BWP. The higher layer parameter (e.g.,firstActiveUplinkBWP-Id) may indicate a first active UL BWP on a servingcell (e.g., secondary cell) or on a supplementary carrier. The wirelessdevice may use the first active UL BWP on the serving cell or on thesupplementary carrier as the respective first active UL BWP.

A wireless device may not expect to transmit HARQ-ACK on a PUCCHresource indicated by a DCI format 1_0 or a DCI format 1_1, for example,based on paired spectrum operation, the wireless device changing itsactive UL BWP on a primary cell between a time of a detection of the DCIformat 1_0 or the DCI format 1_1, and/or a time of a correspondingHARQ-ACK transmission on the PUCCH. A wireless device may not monitorPDCCH when the wireless device performs RRM measurements over abandwidth that is not within the active DL BWP for the wireless device.

A DL BWP index (ID) may be an identifier for a DL BWP. One or moreparameters in an RRC configuration may use the DL BWP-ID to associatethe one or more parameters with the DL BWP. The DL BWP ID of 0 (e.g., DLBWP ID=0) may be associated with the initial DL BWP. An UL BWP index(ID) may be an identifier for an UL BWP. One or more parameters in anRRC configuration may use the UL BWP-ID to associate the one or moreparameters with the UL BWP. The UL BWP ID of 0 (e.g., UL BWP ID=0) maybe associated with the initial UL BWP.

A higher layer parameter (e.g., firstActiveDownlinkBWP-Id) may indicatean ID of a DL BWP to be activated upon performing the reconfiguration,for example, based on a higher layer parameter (e.g.,firstActiveDownlinkBWP-Id) is configured for an SpCell. A higher layerparameter (e.g., firstActiveDownlinkBWP-Id) may indicate an ID of a DLBWP to be used upon MAC-activation of the SCell, for example, based onthe higher layer parameter (e.g., firstActiveDownlinkBWP-Id) beingconfigured for an SCell. A higher layer parameter (e.g.,firstActiveUplinkBWP-Id) may indicate an ID of an UL BWP to be activatedif performing the reconfiguration, for example, based on the higherlayer parameter (e.g., firstActiveUplinkBWP-Id) being configured for anSpCell. A higher layer parameter (e.g., firstActiveUplinkBWP-Id) mayindicate an ID of an UL BWP to be used if MAC-activation of the SCelloccurs, for example, based on a higher layer parameter (e.g.,firstActiveUplinkBWP-Id) being configured for an SCell.

A wireless device, to execute a reconfiguration with sync, may assume(e.g., consider) an uplink BWP indicated in a higher layer parameter(e.g., firstActiveUplinkBWP-Id) to be an active uplink BWP. A wirelessdevice, to execute a reconfiguration with sync, may assume (e.g.,consider) a downlink BWP indicated in a higher layer parameter (e.g.,firstActiveDownlinkBWP-Id) to be an active downlink BWP.

A wireless device may be provided, for a cell (e.g., SCell, PCell, BWP),with a first set of reference signal (RS) resources (e.g., SSB, CSI-RS)by a first higher layer parameter (e.g., failureDetectionResources,RadioLinkMonitoringRS). The wireless device may be provided, for thecell, with a first threshold by a second higher layer parameter (e.g.,rlmInSyncOutOfSyncThreshold). The wireless device may be provided, forthe cell, with one or more parameters by a third higher layer parameter(e.g., BeamFailureRecoveryConfig). The third higher layer parameter maybe for a beam failure detection and/or a beam failure recovery procedureof the cell. The one or more parameters may comprise at least: a beamfailure counter (e.g., beamFailureInstanceMaxCount) for the beam failuredetection, a beam failure detection timer (e.g.,beamFailureDetectionTimer) for the beam failure detection, and/or a beamfailure recovery timer (e.g., beamFailureRecoveryTimer) for the beamfailure recovery procedure.

The wireless device (e.g., via the physical layer) may assess a firstradio link quality (e.g., BLER, L1-RSRP) according to the first set ofRS resources. The wireless device (e.g., via the physical layer) maycompare the assessed quality with the first threshold. The wirelessdevice (e.g., via the physical layer) may provide a beam failureinstance (BFI) indication to a MAC entity of the wireless device, forexample, if the first radio link quality is less (e.g., higher BLER,lower SINR, lower L1-RSRP, etc.) than the first threshold.

The wireless device (e.g., via the physical layer) may provide the BFIindication to the wireless device (e.g., a MAC entity of the wirelessdevice) with a first periodicity. The first periodicity may bedetermined by a maximum of a period of an RS of the first set of RSresources and a second value (e.g., 2 msec or any other duration). TheRS may have the shortest periodicity among the first set of RSresources. The second value may be configured by higher layers (e.g.,RRC). The second value may be predefined and/or fixed. As shown in FIG.26, for example, the periodicity may correspond with T.

The wireless device (e.g., a MAC entity of the wireless device) mayincrement a counter (e.g., BFI_COUNTER, BFI counter in FIG. 26, etc.) byone, for example, based on receiving the BFI indication via the physicallayer. The BFI counter (e.g., BFI_COUNTER) may be a variable used by thewireless device. The BFI counter (e.g., BFI_COUNTER) may be a counterfor a BFI indication. The BFI counter (e.g., BFI_COUNTER) may beinitially set to zero.

The wireless device (e.g., a MAC entity of the wireless device) maystart and/or restart a timer (e.g., the beamFailureDetectionTimer), forexample, based on receiving the BFI indication via the physical layer.The timer (e.g., beamFailureDetectionTimer) may expire. The wirelessdevice may set the BFI counter (e.g., BFI_COUNTER) to zero (or any othervalue) based on the timer (e.g., beamFailureDetectionTimer) expiring.

The wireless device may initiate a random access procedure for a beamfailure recovery of the cell, for example, based on the BFI counter(e.g., BFI_COUNTER) being equal to or greater than a value (e.g.,beamFailureInstanceMaxCount), and/or if the wireless device isconfigured with the third higher layer parameter. The wireless devicemay start the timer (e.g., beamFailureRecoveryTimer) (if configured)based on the random access procedure initiating (or based on the BFIcounter being equal to or greater than the value (e.g.,beamFailureInstanceMaxCount), for example, if the wireless device isconfigured with the third higher layer parameter. The random accessprocedure may be a contention-free random access procedure. The wirelessdevice may initiate a random access procedure for a beam failurerecovery based on the BFI counter (e.g., BFI_COUNTER) being equal to orgreater than a value (e.g., beamFailureInstanceMaxCount), for example,if the wireless device is not configured with the third higher layerparameter. The random access procedure may be a contention-based randomaccess procedure.

A wireless device may perform a BFR procedure on an SpCell (e.g., PCellor PSCell). A base station may send (e.g., transmit), to a wirelessdevice, one or more messages comprising configuration parameters of oneor more cells. The one or more cells may comprise at least onePCell/PSCell and one or more SCells. An SpCell (e.g., PCell or PSCell)and one or more SCells may operate on different frequencies and/ordifferent bands.

An SCell of the one or more SCells may support a multi-beam operation. Awireless device may perform one or more beam management procedures(e.g., a BFR procedure) on and/or for the SCell, in the multi-beamoperation. The wireless device may perform a BFR procedure for theSCell, for example, if at least one of one or more beam pair linksbetween the SCell and the wireless device fails. Previously existing BFRprocedures may result in inefficiencies if there is a beam failure forthe SCell. Previously existing BFR procedures may be inefficient,time-consuming, and/or increase battery power consumption.

BFR procedures for wireless devices as disclosed herein may improvedownlink radio efficiency and/or reduce uplink signaling overhead, forexample, if there is a beam failure for one or more SCells. A BFRprocedure for a wireless device may use first cell random accessresources if a beam failure for an SCell of the one or more SCellsoccurs. A downlink signaling process for a wireless device may be usedfor recovery of a beam failure for an SCell. An uplink signaling processfor a wireless device may be used for a BFR procedure of the SCell.Processes for a wireless device and a base station may include a BFRprocedure for an SCell. Processes for a wireless device and a basestation may reduce resources (e.g., random access resources, preambles,etc.) for the BFR procedure.

A base station may configure a wireless device with an SCell. The SCellmay not have uplink resources. The SCell may comprise downlink-onlyresources (e.g., a downlink-only SCell). The wireless device may nottransmit an uplink signal (e.g., preamble) on the downlink-only SCellfor a BFR procedure of the SCell, based on the SCell not having uplinkresources, for example, if the wireless device detects a beam failure onthe SCell. The wireless device may not perform a BFR procedure on thedownlink-only SCell, for example, if the BFR procedure requires anuplink channel. The base station may not be aware of the beam failure onthe downlink-only SCell, for example, based on the wireless device notperforming the BFR procedure on the SCell. BFR procedures as describedherein for an SCell that comprises downlink-only resources may providesuperior performance, for example, by being performed via another cell.

An SCell may operate at a high frequency (e.g., 23 GHz, 60 GHz, 70 GHz,or any other frequency). An SpCell may operate at a low frequency (e.g.,2.4 GHz, 5 GHz, or any other frequency). The channel condition of theSCell may be different from the channel condition of the SpCell. Thewireless device may use uplink resources of the SpCell to transmit apreamble for a beam failure recovery request for the SCell, for example,to improve robustness of transmission of the preamble. BFR procedures asdescribed herein may provide superior performance, for example, if anSCell operates in a different frequency than a PCell. BFR procedures asdescribed herein may provide superior performance, for example, if adownlink-only SCell uses uplink resources (e.g., random accessresources, uplink BWPs, etc.) of the PCell for a BFR procedure of theSCell.

At least some base stations (e.g., a base station compliant with 3GPPRelease 15 or other technologies) may configure and activate one or morewireless resources such as BFR resources (e.g., preambles, random accessoccasions including time/frequency resources) via one or more RRCmessages (e.g., BFRConfig, RadioLinkMonitoringConfig, etc.). A basestation may configure a wireless device with one or more downlink BWPsof a cell and/or one or more candidate beams of the cell. A BFRprocedure of the cell may specify that one or more PRACH resources(e.g., preamble, time, frequency) for each candidate beam of the one ormore candidate beams of each downlink BWP of the one or more downlinkBWPs of the wireless device may be orthogonal. The one or more PRACHresources may be configured via RRC messages. A wireless device may beconfigured with one or more secondary cells (e.g., SCells) at the sametime (or at different times).

In at least some wireless communication systems, for a BFR procedure ofa PCell, the base station may configure an alternate time/frequencyresource and/or a random access preamble for each candidate beam of thePCell. The wireless device may send a random access preamble to the basestation, and the base station may receive the random access preamble.The base station may become aware of the candidate beam that thewireless device has selected for the BFR procedure of the PCell. Thebase station may have an orthogonal resource allocation with orthogonaltime/frequency resources and candidate beams. The base station maydetermine (e.g., based on this orthogonality) which candidate beam hasbeen selected by the wireless device for the wireless device BFRprocedure of the PCell. The base station may configure the wirelessdevice by an RRC configuration to have orthogonal resource assignments.The base station may configure candidate beams for BFR that areassociated with an orthogonal combination of time, frequency, and/orpreamble values. Each candidate beam may be associated with a differentcombination of time/frequency resources and random access preambles. Thebase station may transmit over different beams to different wirelessdevices simultaneously, for example, without interference problems.Candidate beam 1 may be associated with time 1, frequency 1, andpreamble 1. Candidate beam 2 may be associated with time 2, frequency 2,and preamble 2. If a wireless device executes a BFR and selectscandidate beam 1, the wireless device may transmit preamble 1 with timeresource 1 and frequency resource 1. The base station may determine thatthe wireless device has selected candidate beam 1 for BFR, for example,if the base station receives preamble 1 with time resource 1 andfrequency resource 1.

A wireless device performing BFR procedures for an SCell in the samemanner that legacy systems perform BFR procedures for a PCell may usefar more resources than the BFR procedures described herein. A wirelessdevice may support up to 32 SCells, for example, or up to any othernumber of cells that may be determined (e.g., 64 SCells, 128 SCells, 256SCells, etc.). An orthogonal resource for each candidate beam of the 32SCells (or other quantity of SCells) may greatly increase the resourcerequirements over legacy systems. For example, a system may use 64candidate beams (or a greater quantity of beams), multiplied by fourdownlink BWPs (or a greater quantity of BWPs or other wirelessresources), multiplied by 32 cells (or a greater quantity of cells).Approximately 8,192 orthogonal resources (or a greater quantity oforthogonal resources) may be required for some systems to support BFR ofthe 32 SCells (or a greater quantity of SCells). The more orthogonalresources that are available for candidate beams, the more resources andoverhead that may be required for the BFR procedure in such systems. Ifthe wireless communication system has a shortage of dedicated resources,the resource requirements for candidate beams for BFR procedures withSCells may be a problem.

To avoid a shortage of dedicated resources for BFR and/or improve speedand/or efficiency of the BFR operations, multiple SCells may beconfigured to share resources (e.g., the same time/frequency resourcesand the same random access preambles). To facilitate this sharing ofresources, a new MAC CE is introduced herein that assigns particularresources from a pool of shared resources to particular SCells, so thata particular SCell may be authorized to access the assigned resourcesfrom the pool of shared resources and not other resources. The MAC CEmay provide dynamic orthogonality between the BFR resources. Randomaccess resources to be used for a cell in a beam failure recoveryprocedure may be configured via RRC signaling and activated via a MACCE. Because not all of the SCells may be active at the same time, usingthe MAC CE described herein is beneficial to avoid dedicating resourcesto SCells that are not active. Eight of the SCells may be active at atime, for example, or any quantity less than the maximum quantity ofSCells (e.g., less than 32 SCells) may be active at a time. If an SCellis active, a base station may transmit a MAC CE on the active SCell andactivate candidate beams on the active SCell. The MAC CE may effectivelygroup candidate beams together into sets that may be reused by differentSCells, since only a fraction of the total number of SCells may beactive at any given time. Using the MAC CE reduces the number ofdedicated resources that are required for BFR, thereby reducingcomputational complexity and power consumption, and improving systemefficiency and performance.

FIG. 27 shows an example of a resource configuration for a downlink beamfailure recovery (BFR) procedure. One or more PRACH resources (e.g.,preamble, time, frequency) for each of the one or more candidate beamsof each of the one or more downlink BWPs of each of the one or moresecondary cells may be orthogonal for an exemplary BFR procedure of thewireless device. The base station may configure the one or more PRACHresources via RRC signaling. The base station's configuration andactivation of the one or more BFR resources via RRC may lead to ashortage of dedicated PRACH resources. A few (or more or less) of theone or more secondary cells may be active at a time. The base stationmay not configure orthogonal PRACH resources for the BFR procedure,based on a few secondary cells being active at a time.

A base station may configure one or more BFR resources via RRCsignaling. The base station may activate at least one of the one or moreBFR resources via a MAC CE (e.g., BFR MAC CE) for a BFR procedure of anSCell (e.g., SCell downlink). The base station may configure the sameBFR resources (e.g., preamble, time, frequency) to at least twosecondary cells due to activating the BFR resources via a MAC CE. Atleast two secondary cells may share the same preambles, share the sametime resources, and/or share the same frequency resources. The basestation may guarantee orthogonal PRACH resources via a MAC CEactivation. The base station may activate a cell via a MAC CE, forexample, if the cell is configured to operate in a higher frequency band(e.g., millimeter waves).

A wireless device may move at a high speed, for example, if the wirelessdevice is located in a vehicle that is traveling at a high speed. Awireless device moving at a high speed relative to the associated basestation may result in a beam failure. The base station may send (e.g.,transmit) the MAC CE (e.g., BFR MAC CE) to the wireless device, based onthe wireless device moving at a high speed.

FIG. 28 shows an example of a BFR procedure. Associated with each of theUL BWPs, UL-BWP-1 and UL-BWP-2, of the first cell is a Candidate Beam RSList that may be specified in a BFRConfig configuration for BFR. Each ofthe candidate beams may be indicated and/or identified as aBFR-RS-resource, ranging from 0 to M. Each candidate beamBFR-RS-resource in the Candidate Beam RS List may be associated with anRS index, an RA preamble index, and/or an RA occasion list. Each of thecandidate beams in the Candidate Beam RS List may be associated with adifferent combination of RA preamble and time-frequency occasion. Thetime-frequency occasion may specify a time and frequency resource totransmit the RA preamble. The BFRConfigs for the first cell may bespecified the same as corresponding BFRConfigs for the second cell, forexample, so that the first cell and the second cell share the sameCandidate Beam RS List. The base station may configure the CandidateBeam RS List, and/or may combine the Candidate Beam RS List with a MACCE that is unique for the different cells, so that the MAC CE may selectthe candidate beam for a particular cell (e.g., whether the particularcell is the first cell or the second cell). The base station may specifythe MAC CE to activate at least one candidate beam for a particularcell, for example, a particular SCell. Only the particular SCell forwhich the candidate beam is activated may use the activated candidatebeam. The base station may specify and/or transmit a MAC CE to aparticular SCell, for example, that may activate a particular set ofcandidate beams in the Candidate Beam RS List for the particular SCell.The particular SCell may be limited to using the activated candidatebeams as specified by the MAC CE. The particular SCell may be uniquelyauthorized among all cells to use the activated candidate beamsspecified by the MAC CE for the particular SCell. While all SCells mayshare candidate beam resources with the PCell, the MAC CE may provideorthogonality between all the SCells, for example, so that a particularcandidate beam may be used by just one SCell (and not any other SCell)for candidate beam selection in a BFR procedure. Sharing resourcesbetween the SCells may reduce the total number of candidate beams in asystem, and may reduce the computational and/or memory overheadassociated with a larger number of resources.

A base station may send (e.g., transmit), to a wireless device, one ormore messages comprising configuration parameters for a first cell(e.g., PCell, SCell) and one or more secondary cells. The wirelessdevice may receive, from the base station, the one or more messagescomprising the configuration parameters for a first cell (e.g., PCell,SCell) and one or more secondary cells. The one or more secondary cellsmay comprise a second cell (e.g., SCell). The one or more messages maycomprise one or more RRC messages (e.g., RRC connection reconfigurationmessage, RRC connection reestablishment message, or RRC connection setupmessage).

The configuration parameters for the first cell and one or moresecondary cells may comprise bandwidth part (BWP) configurationparameters for a plurality of BWPs. The plurality of BWPs may comprise afirst plurality of UL BWPs of the first cell. The first plurality of ULBWPs may comprise UL-BWP-1 and UL-BWP-2, for example, as shown in FIG.28. The plurality of BWPs may comprise a second plurality of DL BWPs ofthe second cell. The second plurality of DL BWPs may comprise DL-BWP-1and DL-BWP-2, for example, as shown in FIG. 28.

The configuration parameters for the first cell and one or moresecondary cells may comprise DL-BWP-specific BFR configurationparameters (e.g., RadioLinkMonitoringConfig) on at least one of thesecond plurality of DL BWPs (e.g., DL-BWP-1 and/or DL-BWP-2 shown inFIG. 28) of the second cell. The DL-BWP-specific BFR configurationparameters (BFRConfig) may comprise one or more RSs (e.g.,RadioLinkMonitoringRS) of the at least one of the second plurality of DLBWPs and a beam failure instance (BFI) counter (e.g.,beamFailureInstanceMaxCount) associated with at least one of the secondplurality of DL BWPs. The wireless device may assess the one or more RSs(e.g., SSBs, CSI-RSs). The wireless device may detect a beam failure ofat least one of the second plurality of DL BWPs of the second cell, forexample, based on assessing the one or more RSs and/or based on the BFIcounter. The DL-BWP-1 and DL-BWP-2 may be configured with radio linkmonitoring (RLM) configuration definitions (e.g., RLMConfig).

First DL-BWP-specific BFR configuration parameters configured on theDL-BWP-1 of the second cell may comprise one or more first RSs (e.g.,RadioLinkMonitoringRS) of the DL-BWP-1 and a first BFI counter (e.g.,beamFailureInstanceMaxCount) associated with the DL-BWP-1, for example,as shown in FIG. 28. The wireless device may assess the one or morefirst RSs (e.g., SSBs, CSI-RSs). The wireless device may detect a beamfailure of the DL-BWP-1, based on assessing the one or more first RSsand/or based on the first BFI counter.

Second DL-BWP-specific BFR configuration parameters configured on theDL-BWP-2 of the second cell may comprise one or more second RSs (e.g.,RadioLinkMonitoringRS) of the DL-BWP-2 and a second BFI counter (e.g.,beamFailureInstanceMaxCount) associated with the DL-BWP-2. The wirelessdevice may assess the one or more second RSs (e.g., SSBs, CSI-RSs). Thewireless device may detect a beam failure of the DL-BWP-2, based onassessing the one or more second RSs and/or based on the second BFIcounter.

The configuration parameters for the first cell and one or moresecondary cells may further comprise UL-BWP-specific BFR configurationparameters (e.g., BeamFailureRecoveryConfig) on at least one of thefirst plurality of UL BWPs (e.g., UL-BWP-1 and/or UL-BWP-2 shown in FIG.28) of the first cell. The UL-BWP-specific BFR configuration parametersconfigured on the at least one of the first plurality of UL BWPs maycomprise a candidate beam RS list (e.g., candidateBeamRSList) associatedwith the at least one of the second plurality of DL BWPs of the secondcell (e.g., DL-BWP-1 and/or DL-BWP-2 shown in FIG. 28).

First UL-BWP-specific BFR configuration parameters configured on theUL-BWP-1 (e.g., BFRConfig for DL-BWP-1) may comprise a first candidatebeam RS list (e.g., Candidate Beam RS List) associated with the DL-BWP-1of the second cell, for example, as shown in FIG. 28. SecondUL-BWP-specific BFR configuration parameters configured on the UL-BWP-2(e.g., BFRConfig for DL-BWP-2) may comprise a second candidate beam RSlist (e.g., candidateBeamRSList) associated with the DL-BWP-2 of thesecond cell.

The first candidate beam RS list may comprise one or more BFR-RSresources (e.g., BFR-RS-resource 0, . . . , BFR-RS-resource M shown inFIG. 28). Each of the one or more BFR-RS resources may be associatedwith an RS index (e.g., NZP-CSI-RS-ResourceId, SSB-index), at least onerandom access occasion (e.g., RA occasion list shown in FIG. 28), and/ora preamble index (e.g., RA preamble index shown in FIG. 28). The RSindex associated with each of the one or more BFR-RS resources may bedifferent from the RS indices associated with others of the BFR-RSresources. At least two of the BFR-RS resources may share the same RSindex. The preamble index associated with each of the one or more BFR-RSresources may be different from the preamble indices associated withothers of the BFR-RS resources. At least two of the BFR-RS resources mayshare the same preamble index. The at least one random access occasionassociated with each of the one or more BFR-RS resources may bedifferent from the at least one random access occasions associated withothers of the BFR-RS resources. At least two of the BFR-RS resources mayshare the same at least one random access occasion.

The wireless device may use the RS index to indicate and/or identify anon-zero-power (NZP) CSI-RS resource transmitted in the second cell. TheNZP CSI_RS resource may be transmitted in the first cell, for example,if the first cell and the second cell are QCLed. The base station mayconfigure the NZP-CSI-RS resource in CSI-MeasConfig of the second cell(e.g., for the DL-BWP-1). A wireless device may determine (e.g., basedon the NZP-CSI-RS resource) a candidate beam for a beam failure recovery(BFR) associated with the at least one of the second plurality of DLBWPs of the second cell (e.g., the DL-BWP-1).

The base station may use the CSI-MeasConfig to configure one or moreCSI-RSs (e.g., reference signals) belonging to a serving cell in whichthe CSI-MeasConfig may be included. The base station may use theCSI-MeasConfig to configure channel state information reports to betransmitted on PUCCH on a serving cell in which the CSI-MeasConfig maybe included. The base station may use the CSI-MeasConfig to configurechannel state information reports on PUSCH triggered by DCI received ona serving cell in which the CSI-MeasConfig may be included.

The wireless device may use the RS index to indicate and/or identify anSS/PBCH block within an SS-burst. The SS/PBCH block may determine acandidate beam for a BFR associated with the at least one of the secondplurality of DL BWPs of the second cell (e.g., the DL-BWP-1). Thewireless device may send (e.g., transmit) a preamble, indicated and/oridentified by the preamble index, via the at least one random accessoccasion (e.g., on the UL-BWP-1) to perform the BFR associated with theat least one of the second plurality of DL BWPs of the second cell(e.g., the DL-BWP-1), based on or after selecting a candidate beam(e.g., RS) indicated and/or identified by the RS index.

FIG. 29A shows an exemplary beam failure recovery medium access controlcontrol element (BFR MAC CE). A base station may transmit the BFR MAC CEto configure the beam failure recovery procedures of all wirelessdevices that communicate with the base station via the PCell, and/or ofall SCells that communicate with and/or are controlled by the basestation. The BFR MAC CE is shown as comprising numerous fields arrangedin octets (e.g., units of 8 bits each). Octet 1 may comprise a five-bitfield Serving Cell ID, a two-bit field BWP ID, and/or a one-bit fieldA/D, each of which is explained below. Octets 2 through M+2 may comprisea numbered sequence of eight-bit fields RS ID, which are explainedbelow.

Each BFR MAC CE, based on the included fields, may indicate and/orspecify a subset of BFR-RS-resources, among the pool of BFR-RS-resourcesthat may be shared among all SCells associated with the base station'sPCell. The indicated and/or specified subset may be activated and/ordeactivated for use by a particular BWP that is indicated and/orspecified by the field BWP ID for a particular SCell indicated and/orspecified by the field Serving Cell ID, according to a value of the A/Dbit field. There may be up to 32 SCells associated with a single PCell,four BWPs associated with each of the 32 SCells, and 256BFR-RS-resources (e.g., candidate beams) that are in a pool of candidatebeams shared by all the SCells, based on a quantity of bits allocated tothe different fields. A quantity of BWPs, SCells, and/or candidate beamsshown and described is an example and should not be construed aslimiting. Any quantity of bits in the BWP ID and/or the Serving Cell IDfields may be changed (e.g., increased or decreased) to supportdifferent quantities of BWPs and/or SCells. A base station may send(e.g., transmit) four BFR MAC CEs as shown in FIG. 29A for each SCell,for example, to activate a unique set of candidate beams for a BFRprocedure for each of the BWPs in each of the SCells according to theM+1 specified RS IDs in Octets 2 through M+2. While the pool ofBFR-RS-resources may be shared among all the cells, the BFR MAC CEorthogonally may allocate the BFR-RS-resources to the individual DL BWPsof all the SCells associated with the base station that sends (e.g.,transmits) the BFR MAC CEs. If the base station determines to activateand/or deactivate a particular candidate beam for use by a particularBWP of a particular SCell, the base station may send (e.g., transmit)the BFR MAC CE shown in FIG. 29A, including the RS ID's corresponding tothe candidate beams having a changed activation/deactivation status. Achange in a single candidate beam activation/deactivation status mayrequire less transmission power and/or processing power than an initialspecification of the activation/deactivation status of all the potentialcandidate beams if using the BFR MAC CE format shown in FIG. 29A.

A base station may send (e.g., transmit) a BFR MAC CE, to a wirelessdevice, to activate and/or deactivate one or more BFR-RS resources(e.g., associated PRACH resources, one or more preambles, one or moreRSs, etc.) for the wireless device to use. The BFR MAC CE may beassociated with a logic channel ID (LCID) in a corresponding MAC header.The LCID may indicate that the BFR MAC CE may activate and/or deactivatethe one or more BFR-RS resources. The LCID may indicated and/or identifya logical channel instance of the BFR MAC CE. A size of the LCID maycorrespond to a value (e.g., 6 bits, or any other quantity of bits). TheBFR MAC CE may comprise one or more fields comprising at least one of: afirst field, a second field, a third field, and/or a fourth field.

The first field may indicate an identity of a serving cell (e.g.,Serving Cell ID). A wireless device may apply one or more actions forthe serving cell according to the BFR MAC CE, for example, based on thefirst field indicating the identity of the serving cell. A length of thefirst field may correspond to a first value (e.g., 5 bits, or any otherquantity of bits).

The second field may indicate a BWP index (e.g., BWP ID) of a BWP (e.g.,DL BWP). The BFR MAC CE may apply for the BWP based on the second fieldindicating the BWP index of the BWP. A length of the second field maycorrespond to a second value (e.g., 2 bits, or any other quantity ofbits). A total of four BWPs may be uniquely indicated and/or identifiedby a two-bit-length BWP ID field. Any other quantity of BWPs may beuniquely indicated and/or identified by a BWP ID field comprising acorresponding length (e.g., two BWPs corresponding to a 1-bit length,eight BWPs corresponding to a 3-bit length, sixteen BWPs correspondingto a 4-bit length, etc.).

The third field may indicate one or more RS indices (e.g., RS-ID_0, . .. , RS-ID_M shown in FIG. 29A) associated with the one or more BFR-RSresources (e.g., BFR-RS-resource 0, BFR-RS-resource M shown in FIG. 28).Each of the one or more RS indices may indicate an RS index associatedwith one of the one or more BFR-RS resources, and thereby indicateand/or identify a unique candidate beam for the BFR procedure. RS-ID_0may indicate the BFR-RS-resource 0, and RS-ID_M may indicate theBFR-RS-resource M. A length of the third field may correspond to a thirdvalue (e.g., (M+1)*8 bits, where M+1 is the number of BFR-RS resources).

The fourth field (e.g., A/D) may indicate whether the BFR MAC CE is usedto activate (e.g., “A”) or deactivate (e.g., “D”) the one or more BFR-RSresources indicated by the one or more RS indices. Setting the fourthfield to “1” may indicate activation (e.g., “A”). Setting the fourthfield to “0” may indicate deactivation (e.g., “D”).

The wireless device may activate the BFR-RS-resource 0 associated withthe RS-ID_0, for example, based on the fourth field being set to “1” andthe third field indicating RS-ID_0. The wireless device may deactivatethe BFR-RS-resource 0 associated with the RS-ID_0, for example, based onthe fourth field being set to “0” and the third field indicatingRS-ID_0.

FIG. 29B shows an exemplary BFR MAC CE. A base station may send (e.g.,transmit) the BFR MAC CE to configure the beam failure recoveryprocedures of wireless devices that communicate with the base stationvia the PCell, and of SCells that communicate with and/or are controlledby the base station. The BFR MAC CE is shown as having numerous fieldsarranged in octets (e.g., units of 8 bits each). As shown, Octet 1comprises a five-bit field Serving Cell ID, a two-bit field BWP ID, anda one-bit field R, each of which is explained below. Octets 2 through Ncomprise a numbered sequence of one-bit fields C_i, where i ranges from0 to M, which are explained below.

Each BFR MAC CE, based on the included fields, may specify theactivated/deactivated status of all possible BFR-RS-resources for use bya particular BWP that is indicated and/or specified by the field BWP IDfor a particular SCell indicated and/or specified by the field ServingCell ID. There may be up to 31 SCells associated with a single PCell,four BWPs associated with each of the 31 SCells, and M+1BFR-RS-resources (e.g., candidate beams) that may be in a pool ofcandidate beams shared by all the SCells, based on a quantity of bitsallocated to the different fields. The activated/deactivated status ofeach of the candidate beams may be specified according to a value of acorresponding C_i in a bitmap of C_i's to BFR-RS-resources correspondingto all the potential candidate beams in the pool of candidate beamsshared by all the SCells. For example, for values of the variable iranging from 0 to M, C_i may correspond to and specify theactivation/deactivation status of the BFR-RS-resource i shown in theCandidate Beam RS List in FIG. 28. A value of “1” for C_i may indicatethat the associated candidate beam is activated for the specified BWPand SCell. A value of “0” may indicate that the associated candidatebeam is deactivated for the specified BWP and SCell. The bitmap of C_i'sare presented in Octets 2 through N. A quantity of BWPs, SCells, andcandidate beams shown and described is an example and should not beconstrued as limiting. A quantity of bits in the BWP ID and/or ServingCell ID fields may be changed (e.g., increased or decreased) to supportdifferent quantities of BWPs and/or SCells. A base station may send(e.g., transmit) four BFR MAC CEs (as shown in FIG. 29B) for each SCell,for example, to indicate and/or specify the activated/deactivated statusfor all possible candidate beams for a BFR procedure for each of theBWPs in each of the SCells according to the bitmap of M+1 C_i's inOctets 2 through M+2. While the pool of BFR-RS-resources may be sharedamong all of the cells, the BFR MAC CE orthogonally may allocate theBFR-RS-resources to the individual DL BWPs of all of the SCellsassociated with the base station that sends (e.g., transmits) the BFRMAC CEs. The base station may send (e.g., transmit) the entire BFR MACCE shown in FIG. 29B including the full C_i bitmap corresponding to theentire pool of candidate beams, if the base station determines toactivate and/or deactivate a particular candidate beam for use by aparticular BWP of a particular SCell.

There may be performance trade-offs between the BFR MAC CE formats ofFIG. 29A and FIG. 29B. A change in a single candidate beamactivation/deactivation status may require more transmission powerand/or processing power if using the BFR MAC CE format shown in FIG. 29Bcompared with using the BFR MAC CE format shown in FIG. 29A. The BFR MACCE of FIG. 29B may require less transmission power and/or processingpower compared with the BFR MAC CE format shown in FIG. 29A, forexample, because the format shown in FIG. 29B uses only one bit todesignate the activation/deactivation status for each candidate beam.The BFR MAC CE format shown in FIG. 29A may use a full octet (e.g., 8bits) to designate the activation/deactivation status for each candidatebeam, for example, if specifying the activation/deactivation status forall candidate beams for a particular DL BWP and SCell. A beneficialcompromise may include using the BFR MAC CE format of FIG. 29B ifinitially specifying the activation/deactivation status for eachcandidate beam for each DL BWP of each SCell, and using the BFR MAC CEformat of FIG. 29A if (e.g., later) changing the activation/deactivationstatus of a smaller subset for candidate beams for one or more DL BWPsof one or more SCells.

The BFR MAC CE may comprise at least one of a first field, a secondfield, a third field, and/or a fourth field. The first field (e.g.,Serving Cell ID) and the second field (e.g., BWP ID) may be correspondto the fields described above in regard to FIG. 29A. A length of thethird field may correspond to a third value (e.g., M+1 bits, where M+1is the number of BFR-RS resources) different from that discussed abovein regard to FIG. 29A. The contents of the third field are describedbelow. The fourth field may indicate a reserved bit (e.g., an R field).The reserved bit may be set to zero (or one).

The third field may comprise one or more C-fields (e.g., C_0, . . . ,C_M shown in FIG. 29B). A C_i field of the one or more C-fields mayindicate an activation/deactivation status of a BFR-RS resource i (e.g.,if configured) of the one or more BFR-RS resources (e.g.,BFR-RS-resource 0, . . . , BFR-RS-resource M shown in FIG. 28). A BFR-RSresource i may be activated if the C_i field is set to one. A BFR-RSresource i may be deactivated if the C_i field is set to zero.

The base station may configure M+1 BFR-RS-resources, i.e.,BFR-RS-resource 0 to BFR-RS-resource M, as shown in FIG. 28. Thewireless device may deactivate the BFR-RS-resource 0, for example, ifthe wireless device receives the BFR MAC CE with the C_0 field set tozero. The wireless device may activate the BFR-RS-resource 0, forexample, if the wireless device receives the BFR MAC CE with the C_0field set to one. The wireless device may deactivate the BFR-RS-resourceM, for example, if the wireless device receives the BFR MAC CE with theC_M field set to zero. The wireless device may activate theBFR-RS-resource M, for example, if the wireless device receives the BFRMAC CE with the C_M field set to one. The base station may not configureBFR-RS resource i. The wireless device may ignore the C_i field, forexample, if the base station does not configure BFR-RS resource i.

FIG. 30 shows an example of a downlink BFR procedure. A base station3010 may send (e.g., transmit) to a wireless device 3020, and thewireless device 3020 may receive from the base station 3010, one or moreRRC messages comprising configuration parameters for a first cell (e.g.,PCell) and one or more secondary cells (e.g., SCell) at time T0, asdiscussed above in regard to FIG. 28. The one or more RRC messages mayspecify a candidate beam list (e.g., the full set of candidate beams fora BFR procedure that may be shared among all cells). Because a wirelessdevice receiving the RRC message at time T0 may not know what candidatebeams are activated for each BWP of each SCell with which the wirelessdevice may communicate, the wireless device may not be able to perform aBFR procedure. The wireless device may not monitor for (e.g., mayrefrain from monitoring) a beam failure and/or may not measure (e.g.,may refrain from measuring) any beams, for example, at least until afterreceiving specifications indicating which candidate beams are activatedfor each BWP of each SCell with which the wireless device maycommunicate.

The base station 3010 may send (e.g., transmit) to the wireless device3020, and the wireless device 3020 may receive, a BFR MAC CE (e.g., asdiscussed above in regard to FIG. 29A) at time T1. The first field ofthe BFR MAC CE may indicate a second cell (e.g., SCell). The secondfield of the BFR MAC CE may indicate at least one of the secondplurality of DL BWPs (e.g., the DL-BWP-1 shown in FIG. 28). The thirdfield of the BFR MAC CE may indicate a first RS index associated with afirst BFR-RS resource (e.g., BFR-RS resource 0 shown in FIG. 28) of theone or more BFR-RS resources (e.g., BFR-RS resource 0, . . . , BFR-RSresource M shown in FIG. 28). The first BFR-RS resource may comprise thefirst RS index indicating a first RS (e.g., CSI-RS, SSB), a first randomaccess (RA) occasion, and/or a first preamble index indicating a firstpreamble. The fourth field of the BFR MAC CE may indicate activation(e.g., set to “1”).

The wireless device may activate the first BFR-RS resource, for example,based on the third field of the BFR MAC CE indicating the first RS indexand the fourth field of the BFR MAC CE being set to one. The wirelessdevice may monitor and/or assess the first RS as a candidate beam for aBFR of at least one of the second plurality of DL BWPs (e.g., indicatedby the second field) of the second cell (e.g., indicated by the firstfield), for example, based on the wireless device activating the firstBFR-RS resource. The wireless device may send (e.g., transmit) the firstpreamble via the first RA occasion for a BFR of at least one of thesecond plurality of DL BWPs (e.g., indicated by the second field) of thesecond cell (e.g., indicated by the first field), for example, based onthe wireless device activating the first BFR-RS resource and/or if thewireless device selects the first RS as a candidate beam.

The wireless device may deactivate the first BFR-RS resource, forexample, based on the third field of the BFR MAC CE indicating the firstRS index and/or the fourth field of the BFR MAC CE being set to zero.The wireless device may stop monitoring and/or assessing the first RS asa candidate beam for a BFR of at least one of the second plurality of DLBWPs (e.g., indicated by the second field) of the second cell (e.g.,indicated by the first field), for example, based on deactivating thefirst BFR-RS resource. The wireless device may not transmit the firstpreamble via the first RA occasion for a BFR of the at least one of thesecond plurality of DL BWPs (e.g. indicated by the second field) of thesecond cell (e.g., indicated by the first field), for example, based ondeactivating the first BFR-RS resource.

The wireless device may operate on at least one of the second pluralityof DL BWPs (e.g., DL-BWP-1) at time T2. The at least one of the secondplurality of DL BWPs may be an active DL BWP of the second cell at timeT2.

The wireless device may operate on at least one of the first pluralityof UL BWPs (e.g., UL-BWP-1) at time T2. The at least one of the firstplurality of UL BWPs may be an active UL BWP of the first cell at timeT2.

The wireless device (e.g., via the physical layer) may assess a radiolink quality according to the one or more RSs (e.g.,RadioLinkMonitoringRS) associated with at least one of the secondplurality of DL BWPs (e.g., DL-BWP-1). The wireless device (e.g., viathe physical layer) may compare the assessed quality with a firstthreshold (e.g., rlmInSyncOutOfSyncThreshold). The first threshold(e.g., BLER, L1-RSRP) may correspond to a value provided by a higherlayer (e.g., RRC, MAC). The first threshold may correspond to a valueprovided by the configuration parameters for the first cell (e.g.,PCell) and/or one or more secondary cells (e.g., SCell).

The wireless device (e.g., via the physical layer) may provide a beamfailure instance (BFI) indication to higher layers (e.g., MAC) of thewireless device, for example, if the radio link quality of the one ormore RSs is worse (e.g., higher BLER, lower L1-RSRP, lower SINR) thanthe first threshold. The wireless device may increment a BFI counter(e.g., BFI_COUNTER) by one (e.g., at time T, 2T, 5T as shown in FIG.26), for example, if a higher layer entity (e.g., MAC entity) receivesthe BFI indication via the physical layer of the wireless device. TheBFI counter (e.g., BFI_COUNTER) may be a counter for a BFI indication.The BFI counter (e.g., BFI_COUNTER) may be initially set to zero.

The BFI counter (e.g., BFI_COUNTER) may be equal to or greater than thevalue of BFI counter (e.g., beamFailureInstanceMaxCount), for example,based on incrementing the BFI counter. The wireless device may initiatea random access procedure for a beam failure recovery of at least one ofthe second plurality of DL BWPs of the second cell, for example, basedon or in response to the BFI counter (e.g., BFI_COUNTER) being equal toor greater than the value of BFI counter (e.g.,beamFailureInstanceMaxCount).

The wireless device (e.g., via the physical layer) may assess a secondradio link quality of the first RS (e.g., CSI-RS, SSB) of at least oneof the second plurality of DL BWPs (e.g., DL-BWP-1) against a secondthreshold (e.g., rsrp-ThresholdSSB), for example, based on the thirdfield of the BFR MAC CE indicating the first RS index, and/or if thewireless device initiates the random access procedure. The first RS maybe identified and/or indicated by the first RS index. The secondthreshold (e.g., BLER, L1-RSRP) may correspond to a second valueprovided by a higher layer entity (e.g., RRC, MAC entity). The secondthreshold may correspond to a second value provided by the configurationparameters.

The wireless device may select the first RS as a candidate beam if thesecond radio link quality of the first RS is better (e.g., lower BLER,higher L1-RSRP, higher SINR) than the second threshold. The wirelessdevice may send (e.g., transmit) a first preamble identified and/orindicated by the first preamble index via the first random accessoccasion for the BFR of at least one of the second plurality of DL BWPsof the second cell, for example, based on selecting the first RS, attime T3 shown in FIG. 30.

FIG. 31A and FIG. 31B show examples of a BFR MAC CE. The BFR MAC CE maycomprise one or more fields comprising at least one of a first field, asecond field, a third field, a fourth field, and/or a fifth field. Ofthese fields, the fifth field (e.g., R field) in FIG. 31A and FIG. 31Bmay indicate a reserved bit. The R field may be set to zero (or one).The first through fourth fields are described below.

A base station may send (e.g., transmit) the BFR MAC CE to configure thebeam failure recovery procedures of all wireless devices that maycommunicate with the base station via the PCell, and of all SCells thatcommunicate with and/or are controlled by the base station. The BFR MACCE is shown in two different formats shown in FIG. 31A and FIG. 31B ascomprising numerous fields arranged in octets (e.g., units of 8 bitseach). As shown, Octet 1 comprises a five-bit field Serving Cell ID anda two-bit field BWP ID. In the format of FIG. 31A, Octet 1 alsocomprises a one-bit field A/D, whereas in the format of FIG. 31B, Octet1 instead comprises a one-bit reserved field R. Each of these fields ofOctet 1 is explained below. Octets 2 through M+2 comprise a numberedsequence of six-bit fields Preamble ID_i, where i ranges from 0 to M.The Preamble IDs in Octets 2 through M+2 in the BFR MAC CE formats ofFIG. 31A and FIG. 31B correspond to the random access preamble indexshown in FIG. 28. Entries in the specified random access preamble indexcorrespond to entries in the RS index having a same index value. Awireless device receiving a random access preamble may determine thecorresponding BFR-RS-resource, for example, by mapping the random accesspreamble to an index value in the preamble index, and/or looking up theRS that corresponds to the index value in the RS index.

In the format of FIG. 31A, each Octet 2 through M+2 comprises a two-bitreserved field R in addition to the six-bit field Preamble ID_i. Thesix-bit field Preamble ID_i field may support indicating and/oridentifying up to 64 unique preambles. The reserved field R may providethe capability for expansion to support up to an additional two bitsadded to the Preamble ID_i field to support a total of up to 256Preamble ID's indicated and/or identified by an eight-bit Preamble ID_ifield. All of the Preamble ID's specified in Octets 2 through M+2 maydesignate candidate beams may be activated for the BWP ID and ServingCell ID specified in Octet 1, for example, if the A/D field of Octet 1is set to designate activation of the specified candidate beams (e.g.,by a value of “1”). All of the Preamble ID's specified in Octets 2through M+2 designate candidate beams may be deactivated for the BWP IDand Serving Cell ID specified in Octet 1, for example, if the A/D fieldof Octet 1 is set to designate deactivation of the specified candidatebeams (e.g., by a value of “0”). Any quantity of Preamble IDscorresponding to designated beams may be provided in Octets 2 throughM+2 for a particular BWP ID and Serving Cell ID.

In the format of FIG. 31B, each Octet 2 through M+2 comprises a one-bitreserved field R in addition to the six-bit field Preamble ID_i. Thesix-bit field Preamble ID_i field may support indicating and/oridentifying up to 64 unique preambles. The reserved field R may providethe capability for expansion to support up to an additional one bitadded to the Preamble ID_i field to support a total of up to 128Preamble ID's indicated and/or identified by a seven-bit Preamble ID_ifield. Each of the Preamble ID's specified in Octets 2 through M+2 maydesignate a candidate beam that is to be either activated or deactivatedfor the BWP ID and Serving Cell ID specified in Octet 1, for example,according to a value of the A/D field of the Octet that includes thePreamble ID. The A/D field in a same Octet as Preamble ID_0 may be setto designate activation of the candidate beam corresponding to thePreamble ID_0 (e.g., by a value of “1”). The A/D field in a same Octetas Preamble ID_1 may be set to designate deactivation of the candidatebeam corresponding to the Preamble ID_1 (e.g., by a value of “0”). Eachof the Preamble IDs specified in Octets 2 through M+2 may designatecandidate beams that are to be either activated or deactivated for theBWP ID and Serving Cell ID specified in Octet 1, for example, accordingto a value of their respective corresponding A/D fields with which thePreamble IDs share an Octet. Any number of Preamble IDs corresponding todesignated beams may be provided in Octets 2 through M+2 for aparticular BWP ID and Serving Cell ID.

Each BFR MAC CE, based on the included fields, may indicate and/orspecify a subset of BFR-RS-resources, among the pool of BFR-RS-resourcesthat may be shared among all SCells associated with the base station'sPCell. Members of the indicated and/or specified subset may becollectively activated or deactivated for use by a particular BWP thatis indicated and/or specified by the field BWP ID for a particular SCellindicated and/or specified by the field Serving Cell ID, for example,according to a value of the A/D bit field in Octet 1, in the formatshown in FIG. 31A. Members of the specified subset may be individuallyactivated and/or deactivated for use by a particular BWP that isindicated and/or specified by the field BWP ID for a particular SCellindicated and/or specified by the field Serving Cell ID, for example,according to a value of the A/D bit field in the Octet shared with arespective Preamble ID, in the format shown in FIG. 31B.

There may be up to 31 SCells associated with a single PCell, four BWPsassociated with each of the 31 SCells, and 64 Preamble IDs correspondingto candidate beams that may be in a pool of candidate beams shared byall the SCells, based on a quantity of bits allocated to the differentfields. A quantity of BWPs, SCells, and/or candidate beams shown anddescribed is an example and should not be construed as limiting. Aquantity of bits in the BWP ID and/or Serving Cell ID fields may bechanged (e.g., increased or decreared) to support different quantitiesof BWPs and/or SCells. The reserved bit R in Octet 1 of FIG. 31A may beallocated, for example, to the BWP ID or the Serving Cell ID, toincrease the respective field's addressable range.

A base station may send (e.g., transmit) four BFR MAC CEs as shown inFIG. 31A or FIG. 31B for each SCell, for example, to activate a uniqueset of candidate beams for a BFR procedure for each of the BWPs in eachof the SCells according to the M+1 specified Preamble IDs in Octets 2through M+2. While the pool of BFR-RS-resources may be shared among allthe cells, the BFR MAC CE orthogonally may allocate the BFR-RS-resourcesto the individual BWPs of all the SCells associated with the basestation that sends (e.g., transmits) the BFR MAC CEs. If the basestation determines to collectively activate and/or deactivate one ormore particular candidate beams for use by a particular BWP of aparticular SCell, the base station may send (e.g., transmit) the BFR MACCE shown in FIG. 31A, for example, including the Preamble IDscorresponding to the candidate beams having a same desiredactivation/deactivation status. If the base station determines toindividually activate and/or deactivate one or more particular candidatebeams for use by a particular BWP of a particular SCell, the basestation may send (e.g., transmit) the BFR MAC CE shown in FIG. 31B, forexample, including the Preamble IDs corresponding to the candidate beamshaving a desired new activation/deactivation status. A designation of orchange in a single candidate beam activation/deactivation status mayrequire less transmission power and/or processing power than an initialspecification of the activation/deactivation status of all the potentialcandidate beams if using the BFR MAC CE formats shown in FIG. 31A andFIG. 31B. If some candidate beams are to be activated while othercandidate beams are to be deactivated for a particular BWP ID and aparticular Serving Cell ID, using the BFR MAC CE format of FIG. 31Binstead of FIG. 31A may reduce the number of BFR MAC CEs to be generatedand transmitted, and consequently, may reduce transmission overheadand/or power consumption, because a single BFR MAC CE may both activateand deactivate individual candidate beams associated with the specifiedPreamble IDs.

The first field may indicate an identity of a serving cell (e.g.,Serving Cell ID). The BFR MAC CE may apply for the serving cell based onthe first field indicating the identity of the serving cell. A firstlength of the first field may correspond to a first value (e.g., 5bits).

The second field may indicate a BWP index (e.g., BWP ID) of a BWP (e.g.,downlink BWP). The BFR MAC CE may apply for the BWP, for example, basedon or in response to the second field indicating the BWP index of theBWP. A second length of the second field may correspond to a secondvalue (e.g., 2 bits).

The third field may indicate one or more preamble indices (e.g.,Preamble ID_0, . . . , Preamble ID_M shown in FIG. 31A) associated withthe one or more BFR-RS resources (e.g., BFR-RS-resource 0, . . . ,BFR-RS-resource M shown in FIG. 28). Each of the one or more preambleindices may indicate a preamble index associated with one of the one ormore BFR-RS resources.

Preamble ID_0 may indicate the BFR-RS-resource 0 and Preamble ID_M mayindicate the BFR-RS-resource M. A third length of the third field maycorrespond to a third value (e.g., (M+1)*6 bits, where M+1 is the numberof BFR-RS resources).

The fourth field (e.g., A/D) may indicate whether the BFR MAC CE is usedto activate and/or deactivate the one or more BFR-RS resourcesassociated with the one or more preamble indices. Setting the fourthfield to “1” may indicate activation of the one or more BFR-RS resourcesassociated with the one or more preamble indices, as shown in FIG. 31A.Setting the fourth field to “0” may indicate deactivation the one ormore BFR-RS resources associated with the one or more preamble indices.

Setting the fourth field to “1” may indicate activation of one of theone or more BFR-RS resources associated with one of the one or morepreamble indices, as shown in FIG. 31B. Setting the fourth field to “0”may indicate deactivation of the one of the one or more BFR-RS resourcesassociated with the one of the one or more preamble indices. Thewireless device may deactivate BFR-RS resource (e.g., BFR-RS resource 0shown in FIG. 28) associated with the Preamble ID_0, for example, if thefourth field associated with Preamble ID_0 is zero. The wireless devicemay activate BFR-RS resource (e.g., BFR-RS resource M shown in FIG. 28)associated with the Preamble ID_M, for example, if the fourth fieldassociated with Preamble ID_M is one.

FIG. 32 shows an example of a resource configuration for a downlink BFRprocedure. The example of FIG. 32 is similar to the example of FIG. 28,and descriptions of features in FIG. 28 that are also shown in FIG. 32may also be applicable to the example of FIG. 32. The candidate beam RSlist may comprise one or more BFR-RS resources (e.g., BFR-RS resource 0,. . . , BFR-RS resource M). Each of the one or more BFR-RS resources maycomprise an RS index (e.g., NZP-CSI-RS-ResourceId, SSB-index), at leastone random access occasion (e.g., RA occasion list shown in FIG. 32), apreamble index (e.g., RA preamble index shown in FIG. 32), and/or acandidate RS index (e.g., candidate RS ID shown in FIG. 32).

The candidate RS index format in the example of FIG. 32 may provideadditional capabilities beyond those provided in the example of FIG. 28.A quantity of candidate beams to be indexed may be reduced (e.g., from256 to 64), for example, to reduce a number of bits allocated toindexing the candidate beams (e.g., from 8 bits to 6 bits) by adding theadditional candidate RS index to the BFR-RS-resource.

FIG. 33A and FIG. 33B show examples of a BFR MAC CE. The BFR MAC CE maycomprise one or more fields comprising at least one of a first field, asecond field, a third field, a fourth field, and/or a fifth field. Ofthese fields, the fifth field may indicate an R field. The R field mayindicate a reserved bit. The R field may be set to zero (or one). Thenumber of bits allocated to the R field may change from the quantity ofbits shown to allocate a number of bits to another field sharing a sameoctet as the R field (e.g., the Candidate RS ID field). The firstthrough fourth fields are described below.

The BFR MAC CE format shown in FIG. 33A and FIG. 33B may be similar tothe BFR MAC CE format shown in FIG. 31A and described above, except, forexample, that the format shown in FIG. 33A and FIG. 33B may include acandidate RS ID field in Octets 2 through M+2 in place of the preambleID field included in Octets 2 through M+2 in the format shown in FIG.31A. The descriptions of the fields of the BFR MAC CE format shown inFIG. 31A that are the same as the corresponding fields shown in FIG. 33Aand FIG. 33B may be applicable to FIG. 33A and FIG. 33B. In the BFR MACCE format shown in FIG. 33A, four bits may be allocated to the CandidateRS ID field and/or four bits may be allocated to the reserved R bitfield sharing a same octet as the Candidate RS ID field. In the BFR MACCE format shown in FIG. 33B, six bits may be allocated to the CandidateRS ID field and/or two bits may be allocated to the reserved R bit fieldsharing a same octet as the Candidate RS ID field. A total quantity of16 candidate RS index values may be indicated and/or specified, based onfour bits allocated to the Candidate RS ID field as shown in FIG. 33A. Atotal quantity of 64 candidate RS index values may be indicated and/orspecified, for example, based on six bits allocated to the Candidate RSID field as shown in FIG. 33B.

The first field may indicate an identity of a serving cell (e.g.,Serving Cell ID). The BFR MAC CE may apply for the serving cell, forexample, based on the first field indicating the identity of the servingcell. A length of the first field may correspond to a first value (e.g.,5 bits or any other quantity of bits).

The second field may indicate a BWP index (e.g., BWP ID) of a BWP (e.g.,downlink BWP). The BFR MAC CE may apply for the BWP, for example, basedon the second field indicating the BWP index of the BWP. A length of thesecond field may correspond to a second value (e.g., 2 bits or any otherquantity of bits).

The third field may indicate one or more candidate RS indices (e.g.,Candidate RS-ID_0, . . . , Candidate RS-ID_M shown in FIG. 33A)associated with the one or more BFR-RS resources (e.g., BFR-RS resource0, . . . , BFR-RS resource M shown in FIG. 32). Each of the one or morecandidate RS indices may indicate a candidate RS index associated withone of the one or more BFR-RS resources. Candidate RS-ID_0 may indicatethe BFR-RS-resource 0 and Candidate RS-ID_M may indicate theBFR-RS-resource M. A length of the third field may correspond to a thirdvalue (e.g., (M+1)*log_2(M+1) bits, where M+1 is the number of BFR-RSresources).

The fourth field (e.g., A/D) may indicate whether the BFR MAC CE is usedto activate or deactivate the one or more BFR-RS resources indicated bythe one or more RS indices. Setting the fourth field to “1” may indicateactivation. Setting the fourth field to “0” may indicate deactivation.

FIG. 33C shows an example of a BFR MAC CE. The BFR MAC CE may compriseone or more fields comprising at least one of a first field, a secondfield, a third field, and/or a fourth field. The first field (e.g.,Serving Cell ID) and/or the second field (e.g., BWP ID) may be definedas discussed above in regard to FIG. 33A. The fourth field may indicatean R field. The R field may indicate a reserved bit. The R field may beset to zero (or one). The BFR MAC CE may include a bitmap in the thirdfield (e.g., one or more C-fields as discussed below). A length of thethird field may correspond to a third value (e.g., M+1 bits, where M+1is the quantity of BFR-RS resources).

The format of the BFR MAC CE shown in FIG. 33C may be the same as theformat of the BFR MAC CE shown and described with respect to FIG. 29B,except, for example, that the format shown in FIG. 33C may use thebitmap of C_i to C_M values in Octet 2 through Octet N to representactivation/deactivation status of the candidate beams corresponding tothe mapped candidate RS index entries, whereas in FIG. 29B, the BFR MACCE format may use the bitmap of C_i to C_M values in Octet 2 throughOctet N to represent activation/deactivation status of the candidatebeams corresponding to the mapped BFR-RS-resources.

The third field may comprise one or more C-fields (e.g., C_0, . . . ,C_M shown in FIG. 33C). A C_i field of the one or more C-fields mayindicate an activation and/or deactivation status of BFR-RS resource i(e.g., if configured) of the one or more BFR-RS resources (e.g.,BFR-RS-resource 0, . . . , BFR-RS-resource M shown in FIG. 32). TheBFR-RS resource i may be associated with a candidate RS index i. TheBFR-RS-resource i associated with the candidate RS index i may beactivated, if the C_i field is set to one. The BFR-RS resource iassociated with a candidate RS index i may be deactivated, if the C_ifield is set to zero.

The base station may configure M+1 BFR-RS-resources, for example,BFR-RS-resource 0 to BFR-RS-resource M as shown in FIG. 32. The wirelessdevice may deactivate the BFR-RS-resource 0, for example, if thewireless device receives the BFR MAC CE with C_0 field set to zero. Thewireless device may activate the BFR-RS-resource 0, for example, if thewireless device receives the BFR MAC CE with C_0 field set to one. Thewireless device may deactivate the BFR-RS-resource M, for example, ifthe wireless device receives the BFR MAC CE with C_M field set to zero.The wireless device may activate the BFR-RS-resource M, for example, ifthe wireless device receives the BFR MAC CE with C_M field set to one.The base station may not configure BFR-RS-resource i associated with acandidate RS index i. The wireless device may ignore the C_i field, forexample, based on the base station not configuring the BFR-RS resourcei. C_0 may refer to the first BFR-RS resource configuration (e.g.,BFR-RS resource 0) within the candidate beam RS list. C_1 may refer tothe second BFR-RS resource configuration (e.g., BFR-RS resource 1)within the candidate beam RS list.

FIG. 34 shows an example of a BFR MAC CE. Octet 1 of the BFR MAC CE mayinclude a Serving Cell ID field, a BWP ID field, and/or an A/D field, aspreviously discussed with respect to the BFR MAC CE formats shown inFIG. 29A, FIG. 31A, FIG. 33A, and FIG. 33B. Octets 2 through M+2 mayinclude RS ID_i with i ranging from 0 to M, as previously discussed withrespect to the BFR MAC CE formats shown in FIG. 29A. Octets M+3 through2M+3 may include Preamble ID_i with i ranging from 0 to M, as previouslydiscussed with respect to the BFR MAC CE formats shown in FIG. 31A.Octets M+3 through 2M+3 may include Preamble ID_i with i ranging from 0to M, as previously discussed with respect to the BFR MAC CE formatsshown in FIG. 31A. Octets 2M+4 through MN+3M+N+3 may include RAoccasion_ij with i ranging from 0 to 0 and j ranging from 0 to M.Because the BFR MAC CE provides the RS ID, Preamble ID, and RA occasiondata that make up the candidate beam RS list shown in FIG. 28, thewireless device may determine the candidate beam RS list from the BFRMAC CE format of FIG. 34, for example, if the base station does notprovide configuration parameters via RRC to the wireless device. The RSID values, RA preamble values, and/or RA occasion values may all berelated to one another and provide sufficient information for thewireless device and/or the base station to determine the associated listof candidate beams.

A base station using the BFR MAC CE format of FIG. 34 may provide abenefit of both configuring the full list of candidate beams andactivating selected candidate beams on each of a plurality of associatedwireless devices, for example, without having previously transmitted RRCconfiguration parameters. At least because the size of the BFR MAC CEformat of FIG. 34 may be very large compared to other BFR MAC CEspreviously discussed herein, the BFR MAC CE may have a relatively largeprocessing requirement, and/or may not be used frequently. The BFR MACCE format of FIG. 34 may be well-suited for examples in whichconfiguration of BFR for SCells may not be used.

The configuration parameters (e.g., RRC) for a first cell (e.g., PCell)and/or one or more secondary cells (e.g., SCell) may not provide thewireless device with a candidate beam RS list (e.g., configured on theUL-BWP-1 shown in FIG. 28). The first UL-BWP-specific BFR configurationparameters configured on the UL-BWP-1 (e.g., BFRConfig for DL-BWP-1) maynot comprise a first candidate beam RS list (e.g., Candidate Beam RSList) associated with the DL-BWP-1 of the second cell.

The BFR-MAC CE shown in FIG. 34 may provide the wireless device with thecandidate beam RS list (e.g., configured on the UL-BWP-1 shown in FIG.28). The candidate beam RS list may comprise one or more BFR-RSresources (e.g., BFR-RS-resource 0, . . . , BFR-RS-resource M shown inFIG. 28). Each of the one or more BFR-RS resources may comprise an RSindex (e.g., NZP-CSI-RS-ResourceId, SSB-index), at least one randomaccess occasion (e.g., RA occasion list shown in FIG. 28), and/or apreamble index (e.g., RA preamble index shown in FIG. 28). The BFR MACCE may comprise one or more fields comprising at least one of a firstfield, a second field, a third field, a fourth field, a fifth field, asixth field, and/or a seventh field. Of these fields, the seventh fieldmay indicate an R field. The R field may indicate a reserved bit. The Rfield may be set to zero (or one). A bit-length of the R field may bechanged to facilitate a change in the bit-length of another fieldsharing a same octet as the R field. The first through sixth fields arediscussed below.

The first field may indicate an identity of a serving cell (e.g.,Serving Cell ID). The BFR MAC CE may apply for the serving cell, forexample, based on the first field indicating the identity of the servingcell. A length of the first field may correspond to a first value (e.g.,5 bits or any other quantity of bits).

The second field may indicate a BWP index (e.g., BWP ID) of a BWP (e.g.,downlink BWP). The BFR MAC CE may apply for the BWP, for example, basedon the second field indicating the BWP index of the BWP. A length of thesecond field may correspond to a second value (e.g., 2 bits or any otherquantity of bits).

The third field may indicate one or more RS indices (e.g., RS-ID_0, . .. , RS-ID_M shown in FIG. 34) associated with the one or more BFR-RSresources (e.g., BFR-RS-resource 0, . . . , BFR-RS-resource M shown inFIG. 28). Each of the one or more RS indices may indicate an RS indexassociated with one of the one or more BFR-RS resources. RS-ID_0 mayindicate the BFR-RS-resource 0 and RS-ID_M may indicate theBFR-RS-resource M. A length of the third field may be a third value(e.g., (M+1)*8 bits, where M+1 is the number of BFR-RS resources).

The fourth field may indicate one or more preamble indices (e.g.,Preamble ID_0, . . . , Preamble ID_M shown in FIG. 34) associated withthe one or more BFR-RS resources (e.g., BFR-RS-resource 0, . . . ,BFR-RS-resource M shown in FIG. 28). Each of the one or more preambleindices may indicate a preamble index associated with one of the one ormore BFR-RS resources. Preamble ID_0 may indicate the BFR-RS-resource 0and Preamble ID_M may indicate the BFR-RS-resource M. A length of thethird field may be a third value (e.g., (M+1)*6 bits, where M+1 is thenumber of BFR-RS resources).

The fifth field may indicate one or more random access occasions (e.g.,RA occasion_00, RA occasion_0N . . . , RA occasion_MN shown in FIG. 34)associated with the one or more BFR-RS resources (e.g., BFR-RS-resource0, . . . , BFR-RS-resource M shown in FIG. 28). RA occasion_00 to RAoccasion_0N may indicate the BFR-RS-resource 0. RA occasion_M0 to RAoccasion_MN may indicate the BFR-RS-resource M. A length of the fifthfield may correspond to a fifth value (e.g., (M+1)*(N+1)*9 bits, whereM+1 is the number of BFR-RS resources and N+1 is the number of randomaccess occasions per candidate beam).

RS-ID_0, Preamble ID_0, and RA occasion_00 to RA occasion_0N may beassociated, as shown in FIG. 34. One of the one or more BFR-RS resources(e.g., BFR-RS-resource 0) may comprise the RS-ID_0, the Preamble ID_0,and the RA occasion_00 to the RA occasion_0N. RS-ID_M, Preamble ID_M,and RA occasion_M0 to RA occasion_MN may be associated, as shown in FIG.34. One of the one or more BFR-RS resources (e.g., BFR-RS-resource M)may comprise the RS-ID_M, the Preamble ID_M, and the RA occasion_M0 tothe RA occasion_MN.

The sixth field (e.g., A/D) may indicate whether the BFR MAC CE is usedto activate or deactivate the one or more BFR-RS resources indicated byat least one of the fields (e.g., the third field, the fourth field, thefifth field, etc.). Setting the sixth field to “1” may indicateactivation. Setting the sixth field to “0” may indicate deactivation.

FIG. 35 shows an example of a BFR MAC CE. A base station may send (e.g.,transmit) the BFR MAC CE to configure the beam failure recoveryprocedures of wireless devices that communicate with the base stationvia the PCell, and/or to configure SCells that communicate with and/orare controlled by the base station. The BFR MAC CE format shown in FIG.35 may differ from the BFR MAC CE formats shown in FIG. 29A, FIG. 29B,FIG. 31A, FIG. 31B, FIG. 33A, FIG. 33B, FIG. 33C, and FIG. 34 in thatthe BFR MAC CE of FIG. 35 may configure the candidate beams for a BFRprocedure of multiple or all BWPs of a cell identified in a Serving CellID field in Octet 1 of the single BFR MAC CE. The base station may send(e.g., transmit) a single BFR MAC CE as shown in FIG. 35 to do the workof multiple (e.g., four) different BFR MAC CE transmissions using theBFR MAC CE formats discussed above. A base station using the BFR MAC CEformat of FIG. 35 may reduce transmission overhead and/or powerconsumption compared to using the other BFR MAC CE formats discussedabove.

The BFR MAC CE of FIG. 35 is shown as comprising numerous fieldsarranged in octets (e.g., units of 8 bits each). Octet 1 comprises afive-bit field Serving Cell ID and a portion of a bitmap of C_iconfiguration bits for i ranging from 0 to 3, with each C_i designatingwhether a BFR MAC CE payload may be included in the BFR MAC CE for acorresponding BWP of four BWPs of the cell designated in the ServingCell ID field. The bitmap of C_i configuration bits may be split betweenOctet 1 and Octet 2, or completely included in one of the Octet 1 orOctet 2 by changing a location and/or number of bits designated for thereserved field R and depending on a number of BWPs are included in acell. The bitmap of C_i fields to BWPs of the cell may be one-to-one,such that there is one C_i entry for each of the BWPs in a cell. FourC_i fields may correspond to the four BWPs of the cell indicated and/oridentified in the Serving Cell ID field. Each C_i bit may designatewhether a BFR MAC CE payload included in the full BFR MAC CE is to beapplied to the corresponding BWP of the cell indicated and/or identifiedby the Serving Cell ID field. A C_i value of “1” may designate that theBFR MAC CE payload is to be applied to the corresponding BWP, and/or aC_i value of “0” may designate that the BFR MAC CE payload is not to beapplied to the corresponding BWP.

Following Octet 2, a series of BFR MAC CE payloads for each of the BWP'sof the cell identified by the Serving Cell ID field may be included. Atotal length of the BFR MAC CE format of FIG. 35 may be reduced by onlyincluding, following Octet 2, a series of BFR MAC CE payloadscorresponding to each of the C_i bits that indicated that a BFR MAC CEpayload is to be applied to the corresponding BWP of the cell identifiedby the Serving Cell ID field. The BFR MAC CE payload may be definedaccording to any of the BFR MAC CE formats described above in FIG. 29A,FIG. 29B, FIG. 31A, FIG. 31B, FIG. 33A, FIG. 33B, FIG. 33C, or FIG. 34,except, for example, that the BFR MAC CE payload may not include a fielddesignating the BWP to which the payload applies, because thatinformation may be provided by the C_i bitmap of the full BFR MAC CE.The BFR MAC CE may comprise one or more fields comprising at least oneof a first field, a second field, a third field, and/or a fourth field,as described in greater detail below.

The first field may indicate an identity of a serving cell (e.g.,Serving Cell ID). The BFR MAC CE may apply for the serving cell, forexample, based on or in response to the first field indicating theidentity of the serving cell. A first length of the first field maycorrespond to a first value (e.g., 5 bits or any quantity of bits).

The second field may indicate one or more C-fields (e.g., C_0, . . . ,C_3 shown in FIG. 35). A C_i field of the one or more C-fields may beassociated with a BWP indicated and/or identified with a BWP index i(e.g., BWP-ID is equal to i). The C_i field may indicate an activationand/or deactivation status of a BFR MAC CE for the BWP.

The BFR MAC CE may be one of the MAC CEs discussed above in regard toFIG. 29A, FIG. 29B, FIG. 31A, FIG. 31B, FIG. 33A, FIG. 33B, FIG. 33C,and FIG. 34. The wireless device may activate one or more BFR-RSresources indicated by BFR MAC CE, if the C_i field is set to one. TheBFR MAC CE may apply for the BWP with the BWP index i (e.g., BFR MAC CEfor BWP-i shown in FIG. 35). The wireless device may deactivate one ormore BFR-RS resources indicated by BFR MAC CE, for example, if the C_ifield is set to zero. The BFR MAC CE may apply for the BWP with the BWPindex i.

FIG. 36 shows an example of a downlink BFR procedure. A base station3610 may send (e.g., transmit) to a wireless device 3620, and thewireless device 3620 may receive from the base station 3610, one or moreRRC messages comprising the configuration parameters for a first cell(e.g., PCell) and one or more secondary cells (e.g., SCell) at time T0,as discussed above in regard to FIG. 30. The wireless device 3620 mayoperate on at least one of the second plurality of DL BWPs (e.g.,DL-BWP-1). The at least one of the second plurality of DL BWPs may be anactive DL BWP of the second cell.

A wireless device 3620 (e.g., via the physical layer) may startassessing a radio link quality according to the one or more RSs (e.g.,RadioLinkMonitoringRS) associated with the at least one of the secondplurality of DL BWPs (e.g., DL-BWP-1) against the first threshold (e.g.,rlmInSyncOutOfSyncThreshold), for example, based on receiving the BFRMAC CE activating one or more BFR-RS resources at time T1. The wirelessdevice 3620 (e.g., via the physical layer) may start assessing a radiolink quality according to the one or more RSs (e.g.,RadioLinkMonitoringRS) associated with the at least one of the secondplurality of DL BWPs (e.g., DL-BWP-1) against the first threshold (e.g.,rlmInSyncOutOfSyncThreshold), for example, if there are no activatedBFR-RS resources for the at least one of the second plurality of DLBWPs, and/or based on receiving the BFR MAC CE activating one or moreBFR-RS resources. Starting assessing the radio link quality in responseto receiving the BFR MAC CE may save power for the wireless device 3620.

The wireless device 3620 may not receive the BFR MAC CE activating atleast one of the one or more BFR-RS resources for the at least one ofthe second plurality of DL BWPs (e.g., before time T1 shown in FIG. 36).The wireless device 3620 may not assess a radio link quality accordingto the one or more RSs (e.g., RadioLinkMonitoringRS) associated with theat least one of the second plurality of DL BWPs (e.g., between time T0and time T1 shown in FIG. 36), for example, based on not receiving theBFR MAC CE. The wireless device 3620 may not assess a radio link qualityaccording to the one or more RSs (e.g., RadioLinkMonitoringRS)associated with the at least one of the second plurality of DL BWPsbefore being activated by the BFR MAC CE (e.g., time T1 shown in FIG.36). The wireless device 3620 (e.g., via the physical layer) may startassessing a radio link quality according to the one or more RSs (e.g.,RadioLinkMonitoringRS) associated with the at least one of the secondplurality of DL BWPs (e.g., DL-BWP-1) against the first threshold (e.g.,rlmInSyncOutOfSyncThreshold).

The wireless device 3620 (e.g., via the physical layer) may provide abeam failure instance (BFI) indication to higher layer entities (e.g.MAC entity), for example, if the radio link quality of the one or moreRSs is worse (e.g., higher BLER, lower L1-RSRP, lower SINR) than thefirst threshold. The wireless device 3620 may increment a BFI counter(e.g., BFI_COUNTER) by one (e.g., at time T, 2T, 5T as shown in FIG.26), for example, if the higher layer entities (e.g. MAC entity) of thewireless device 3620 receives the BFI indication via the physical layer,for example, based on receiving the BFR MAC CE activating at least oneof the one or more BFR-RS resources for the at least one of the secondplurality of DL BWPs (e.g., time T1 shown in FIG. 36). The wirelessdevice 3620 may increment the BFI counter (e.g., BFI_COUNTER) by one(e.g., at time T, 2T, 5T as shown in FIG. 26), for example, if thehigher layer entities (e.g. MAC entity) of the wireless device 3620receive the BFI indication via the physical layer and/or if there are noactivated BFR-RS resources for the at least one of the second pluralityof DL BWPs, for example, based on receiving the BFR MAC CE activating atleast one of the one or more BFR-RS resources for the at least one ofthe second plurality of DL BWPs (e.g., time T1 shown in FIG. 36).

The wireless device 3620 may not receive the BFR MAC CE activating atleast one of the one or more BFR-RS resources for the at least one ofthe second plurality of DL BWPs (e.g., before time T1 shown in FIG. 36).The wireless device 3620 may not increment the BFI counter (e.g.,BFI_COUNTER) by one based on not receiving the BFR MAC CE. The wirelessdevice 3620 may not may increment the BFI counter (e.g., BFI_COUNTER) byone before being activated by the BFR MAC CE (e.g., between time T0 andtime T1 shown in FIG. 36).

The wireless device 3620 may initiate a random access procedure for abeam failure recovery of the cell, for example, based on the BFI counter(e.g., BFI_COUNTER) being equal to or greater than a value (e.g.,beamFailureInstanceMaxCount) and/or based on receiving the BFR MAC CEactivating one or more BFR-RS resources (e.g., at time T1 shown in FIG.36). The wireless device 3620 may initiate a random access procedure fora beam failure recovery of the cell based on the BFI counter (e.g.,BFI_COUNTER) being equal to or greater than a value (e.g.,beamFailureInstanceMaxCount) and/or based on receiving the BFR MAC CEactivating one or more BFR-RS resources (e.g., at time T1 shown in FIG.36), for example, if there are no activated BFR-RS resources for the atleast one of the second plurality of DL BWP.

The wireless device 3620 may not receive the BFR MAC CE activating atleast one of the one or more BFR-RS resources for the at least one ofthe second plurality of DL BWPs (e.g., before time T1 shown in FIG. 36).The wireless device may not initiate a random access procedure for abeam failure recovery of the cell based on not receiving the BFR MAC CEand/or based on the BFI counter (e.g., BFI_COUNTER) being equal to orgreater than a value (e.g., beamFailureInstanceMaxCount). The wirelessdevice 3620 may set the BFI counter (e.g., BFI_COUNTER) to zero (oranother value), for example, based on receiving the BFR MAC CEactivating one or more BFR-RS resources. The wireless device 3620 mayset the BFI counter (e.g., BFI_COUNTER) to zero (or another value), forexample, based on receiving the BFR MAC CE deactivating one or moreBFR-RS resources.

A base station 3610 may configure a wireless device 3620 with one ormore cells comprising a first cell (e.g., SCell). The base station 3610may activate, hibernate, and/or deactivate the first cell. The basestation 3610 may send (e.g., transmit), to the wireless device 3620, andthe wireless device 3620 may receive, one or more MAC CE(s), foradjusting and/or transitioning of the first cell to a power saving state(e.g., dormant state, such as in FIG. 22). The wireless device 3620 mayadjust and/or transition first the cell to a power saving state (e.g.,dormant state) based on receiving the one or more MAC CE(s). The basestation 3610 may send (e.g., transmit) one or more RRC messagescomprising parameters. The parameters may indicate an scell stateindicator (e.g., sCellState) associated with the cell. The scell stateindicator may be set to a power saving state (e.g., a dormant state).The wireless device 3620 may adjust and/or transition the cell to thepower saving state, for example, based on the scell state indicatorbeing set to the power saving state.

An SCell hibernation timer (e.g., sCellHibernationTimer) associated withthe first cell may expire. The wireless device 3620 may adjust and/ortransition the first cell to a power saving state (e.g., a dormantstate, such as in FIG. 23), for example, based on the SCell hibernationtimer expiring. The wireless device 3620 may not monitor PDCCH on thecell, for example, if the cell is in a power saving state (e.g., adormant state). The wireless device 3620 may not monitor PDCCH for thecell, for example, if the cell is in a power saving state (e.g., adormant state). The wireless device 3620 may (re-)start a power savingand/or dormant SCell deactivation timer (e.g.,dormantSCellDeactivationTimer) of the first cell based on transiting thecell into the power saving state (e.g., dormant state).

FIG. 37 shows an example of a downlink beam failure recovery procedure.A base station 3710 may send (e.g., transmit) to a wireless device 3720,and the wireless device 3720 may receive from the base station 3710, oneor more RRC messages comprising the configuration parameters for a firstcell (e.g., PCell) and one or more secondary cells (e.g., SCell) at timeT0, such as discussed above in regard to FIG. 30. The wireless device3720 may not perform a BFR procedure for a channel controlled by a cellthat is in a power saving state (e.g., a dormant state). The wirelessdevice 3720 may not monitor the channel controlled by a cell that is ina power saving state (e.g., a dormant state) for a beam failure. Thewireless device 3720 may not utilize configured BFR resources forchannels controlled by cells that are in a power saving state (e.g., adormant state), and configured BFR resources that are not utilized maybe inactive. The wireless device 3720 may proactively and/orautonomously release back to the base station any configured BFRresources corresponding to a cell that is in a power saving state (e.g.,a dormant state). The base station 3710 may reassign released BFRresources, that may have previously been assigned to a cell that is in apower saving state (e.g., a dormant state), to another cell. The basestation 3710 may not send (e.g., transmit) a BFR MAC CE or an RRC todeactivate BFR resources that are assigned to a cell that is in a powersaving state (e.g., a dormant state), for example, if the wirelessdevice 3720 proactively releases, to the base station 3710, the BFRresources that were assigned to a cell that is in the power savingstate. Unutilized BFR resources may be reallocated, which may increaseoverall resource utilization efficiency. Transmission overhead for thebase station 3710 may be reduced by the wireless device 3720 proactivelyreleasing the unutilized BFR resources to the base station 3710.

The wireless device 3720 may be configured with the first higher layerparameter, the second layer parameter, and/or the third layer parameter(e.g., at time T0 shown in FIG. 37) for a cell (e.g., SCell, BWP). Thewireless device 3720 may initiate a random access procedure for a beamfailure recovery of the cell, for example, based on or in response to aBFI counter (e.g., BFI_COUNTER) being equal to or greater than a value(e.g., beamFailureInstanceMaxCount), for example, at time T1 shown inFIG. 37.

The wireless device 3720 may adjust and/or transition the cell to apower saving state (e.g., a dormant state), for example, at time T2shown in FIG. 37. The wireless device 3720 may be triggered to adjustedand/or transition the cell based on an SCell hibernation timerassociated with the cell expiring (e.g., as shown in FIG. 23). Thewireless device 3720 may be triggered to adjust and/or transition thecell, based on receiving one or more MAC CE(s) from the base station3710, to the power saving state (e.g., dormant state) such as shown inFIG. 22. The wireless device 3720 may be triggered to adjust and/ortransition the cell, for example, based on receiving one or more RRCmessages comprising parameters from the base station 3710. Theparameters may indicate an scell state indicator set to a power savingstate (e.g., a dormant state).

The wireless device 3720 may release at least one of the configurationparameters (e.g., candidate beam RS list, preambles, RA occasion list,etc.) for the beam failure recovery of the cell, based on the wirelessdevice 3720 adjusting and/or transitioning the cell to a power savingstate (e.g., a dormant state). The wireless device 3720 may release atleast one of the UL-BWP-specific BFR configuration parameters (e.g.,candidate beam RS list, preambles, RA occasion list, etc.) for the beamfailure recovery of the cell, based on the wireless device 3720adjusting and/or transitioning the cell to the power saving state (e.g.,dormant state).

The wireless device 3720 may deactivate the cell (e.g., at time T2 shownin FIG. 37). The wireless device 3720 may be triggered to deactivate thecell based on an SCell deactivation timer associated with the cellexpiring (e.g., as shown in FIG. 23). The wireless device 3720 may betriggered to deactivate the cell based on receiving one or more MACCE(s) from the base station 3710, for adjusting and/or transitioning thecell to an inactive state (e.g., as shown in FIG. 22). The wirelessdevice 3720 may be triggered to deactivate the cell based on receivingone or more RRC messages comprising parameters from the base station3710. The parameters may indicate an scell state indicator set toinactive (e.g., deactivated) state.

The wireless device 3720 may release at least one of the configurationparameters (e.g., candidate beam RS list, preambles, RA occasion list,etc.) for the beam failure recovery of the cell, for example, based onthe wireless device 3720 deactivating the cell. The wireless device 3720may release at least one of the UL-BWP-specific BFR configurationparameters (e.g., candidate beam RS list, preambles, RA occasion list,etc.) for the beam failure recovery of the cell, for example, based onthe wireless device 3720 deactivating the cell.

FIG. 38 shows an example flowchart of a downlink beam failure recoveryprocedure. At step 3810, a wireless device may receive, from a basestation, one or more messages. The one or more messages may comprise oneor more configuration parameters of a first cell and a second cell. Thefirst cell may comprise a first plurality of uplink bandwidth parts(BWPs) comprising an uplink BWP. The second cell may comprise a secondplurality of downlink BWPs comprising a downlink BWP.

The one or more configuration parameters may indicate one or more beamfailure recovery reference signal (BFR-RS) resources for a beam failurerecovery (BFR) of the downlink BWP of the secondary cell. The basestation may configure the BFR-RS resources on the uplink BWP of thefirst cell. Each of the one or more BFR-RS resources may comprise atleast one of: a reference signal (RS) index of a candidate beam, atleast one random access occasion, and/or a preamble index.

At step 3820, the wireless device may check to see whether a beamfailure recovery medium access control control element (BFR MAC CE) hasbeen received. If the wireless device has not received a BFR MAC CE,then at step 3830, the wireless device may not perform a beam failurerecovery procedure using the first BFR-RS resource. The wireless devicemay continue to check to see whether a BFR MAC CE has been received atstep 3820 (e.g., repeating step 3820). If the wireless device hasreceived a BFR MAC CE, then at step 3840, the wireless device mayperform a beam failure recovery procedure using the first BFR-RSresource.

The BFR MAC CE may comprise one or more fields. The one or more fieldsmay comprise a first field, a second field, a third field, and/or afourth field. The first field may indicate the second cell. The secondfield may indicate the downlink BWP of the second cell. The third fieldmay indicate a first BFR-RS resource of the one or more BFR-RSresources. The fourth field may indicate an activation of the firstBFR-RS resource.

The first BFR-RS resource may comprise a first RS index, a firstpreamble index, and/or at least one random access occasion on the uplinkBWP of the first cell. The first RS index may indicate a first RS (e.g.,CSI-RS, SSB). The first preamble index may indicate a first preamble.The at least one random access occasion may comprise one or more timeresources and/or one or more frequency resources.

The one or more configuration parameters may indicate one or more firstreference signals (RSs) of the downlink BWP of the second cell, one ormore second RSs of the downlink BWP of the second cell, and/or a maximumbeam failure instance (BFI) count (e.g., beamFailureInstanceMaxCount)associated with the downlink BWP of the second cell. The one or morefirst RSs may comprise one or more first CSI-RSs and/or one or morefirst SS blocks. The one or more second RSs may comprise one or moresecond CSI-RSs and/or one or more second SS blocks. The first RSassociated with the first BFR-RS resource may be one of the one or moresecondary RSs. The one or more configuration parameters may indicate anassociation between each of the one or more second RSs and each of theone or more BFR-RS resources. A first RS of the one or more second RSsmay be associated with a first BFR-RS resource of the one or more BFR-RSresources. A second RS of the one or more second RSs may be associatedwith a second BFR-RS resource of the one or more BFR-RS resources. Theassociation may be one-to-one.

A wireless device (e.g., via a physical layer) may assess a first radiolink quality (e.g., BLER, L1-RSRP) according to the one or more firstRSs against a first threshold. The first threshold may be based onhypothetical BLER, L1-RSRP, RSRQ, or SINR. The first threshold may beindicated by the one or more configuration parameters. The wirelessdevice (e.g., via the physical layer) may provide a beam failureinstance (BFI) indication to a MAC entity of the wireless device, forexample, if the first radio link quality is worse (e.g., higher BLER,lower SINR, lower L1-RSRP, etc.) than the first threshold.

The wireless device (e.g., a MAC entity of the wireless device) mayincrement a BFI counter (e.g., BFI_COUNTER) by one, based on thewireless device receiving the BFI indication via the physical layer. TheBFI counter may be a variable used by the wireless device. The BFIcounter may be a counter for a BFI indication. The BFI counter may beinitially set to zero.

The wireless device may initiate a random access procedure for a BFR ofthe downlink BWP of the second cell, for example, based on the BFIcounter being equal to or greater than the maximum BFI counter. Thewireless device may assess a second radio link quality of the first RSof the first BFR-RS resource (e.g., if the wireless device initiates therandom access procedure), for example, based on the BFR MAC CEindicating the activation of the first BFR-RS resource.

The wireless device may select the first RS as a candidate beam, forexample, based on or in response to assessing that the second radio linkquality of the first RS is better (e.g., higher L1-RSRP, lower BLER)than a second threshold. The second threshold may be based onhypothetical BLER, RSRP, RSRQ, or SINR. The second threshold may beindicated by the one or more configuration parameters. The wirelessdevice may send (e.g., transmit) the first preamble via the at least onerandom access occasion of the uplink BWP of the first cell for the BFRof the downlink BWP of the secondary cell, for example, based on thewireless device selecting the first RS as the candidate beam. Thewireless device may send (e.g., transmit) the first preamble via the atleast one random access occasion of the uplink BWP of the first cell forthe BFR of the downlink BWP of the secondary cell, for example, based onthe wireless device selecting the first RS as the candidate beam and/orthe BFR MAC CE indicating the activation of: the first preamble and/orthe at least one random access occasion associated with the first BFR-RSresource.

FIG. 39 shows an example flowchart of a downlink beam failure recoveryconfiguration procedure. At step 3910, a base station may send (e.g.,transmit), to one or more wireless devices, one or more RRCconfiguration messages comprising one or more configuration parameters.The one or more configuration parameters may indicate one or more beamfailure recovery reference signal (BFR-RS) resources for a beam failurerecovery (BFR) of a downlink BWP of a secondary cell. The base stationmay configure the BFR-RS resources on the uplink BWP of the first cell.Each of the one or more BFR-RS resources may comprise at least one of: areference signal (RS) index of a candidate beam, a random accessoccasion, and/or a preamble index.

At step 3920, the base station may determine an allocation of BFR-RSresources to different BWPs and/or different cells. The allocation ofBFR-RS resources may uniquely assign a candidate beam to a BWP of acell. The allocation of BFR-RS resources may assign a candidate beam toeach active BWP of each active cell.

At step 3930, the base station may send (e.g., transmit), to one or morewireless devices, a BFR MAC CE indicating and/or specifying thedetermined allocations of BFR-RS resources. The base station may send(e.g., transmit) at least one BFR MAC CE for each active cell. The atleast one BFR MAC CE may be in a format corresponding to a BFR MAC CE asdescribed above with respect to FIG. 29A, FIG. 29B, FIG. 31A, FIG. 31B,FIG. 33A, FIG. 33B, FIG. 33C, FIG. 34, and/or FIG. 35.

A wireless device may receive one or more configuration parameters forone or more secondary cells. The one or more configuration parametersmay indicate a plurality of beam failure recovery request (BFRQ)resources. The wireless device may receive a medium access control (MAC)control element (CE). The MAC CE may comprise a first field indicating acell of the one or more secondary cells. The MAC CE may comprise asecond field indicating at least one BFRQ resource of the plurality ofBFRQ resources. The wireless device may determine to perform a randomaccess procedure for a beam failure recovery of the cell. The wirelessdevice may determine, based on the at least one BFRQ resource and forthe random access procedure, at least one preamble and at least onerandom access channel resource. The wireless device may transmit, viathe at least one random access channel, the at least one preamble. TheMAC CE may further comprise a third field indicating a downlinkbandwidth part (BWP) of the cell. The random access procedure for thebeam failure recovery of the cell may be for a downlink bandwidth partof the cell. The plurality of BFRQ resources may comprise a firstquantity of BFRQ resources. At least one BFRQ resource may be among asecond quantity of orthogonal BFRQ resources that are each indicated bya unique value of the second field. The second quantity of orthogonalBFRQ resources may be less than the first quantity of BFRQ resources.The wireless device may further determine, based on the MAC CE, toactivate a first BFRQ resource of the at least one BFRQ resource. Thewireless device may further determine, based on the MAC CE, todeactivate the first BFRQ resource. The wireless device may further,based on detecting a beam failure before receiving a second MAC CE,refrain from performing a second random access procedure for a secondbeam failure recovery of the cell. The at least one BFRQ resource may beassociated with a first reference signal of one or more referencesignals for a candidate beam selection. The determining the at least onerandom access channel resource may further be based on the firstreference signal. The second field indicating the at least one BFRQresource of the plurality of BFRQ resources may further indicate apreamble index associated with the at least one BFRQ resource. Thedetermining the at least one preamble may further be based on thepreamble index. The MAC CE may further comprise one or more first fieldsindicating a cell of the one or more secondary cells. The MAC CE mayfurther comprise one or more second fields indicating at least one BFRQresource of the plurality of BFRQ resources. The MAC CE may furthercomprise one or more third fields indicating a downlink bandwidth part(BWP) of the cell. The random access procedure for the beam failurerecovery of the cell may be for the downlink BWP of the cell. Thedetermining the at least one preamble may further be based on the one ormore first fields. The determining the at least one preamble may furtherbe based on the one or more second fields. The transmitting the at leastone preamble may further be via an uplink BWP associated with thedownlink BWP of the cell. The second field or the one or more secondfields indicating the at least one BFRQ resource of the plurality ofBFRQ resources may further indicate a preamble index associated with theat least one BFRQ resource. The determining the at least one preamblemay further be based on the preamble index. The wireless device maydetermine, based on the at least one BFRQ resource, at least one randomaccess channel resource of an uplink BWP, associated with a downlink BWPindicated by a third field of the MAC CE, for the transmitting the atleast one preamble. The wireless device may further detect a beamfailure. Detecting the beam failure may comprise providing a beamfailure instance indication based on assessing one or more referencesignals, associated with the at least one BFRQ resource, to have radioquality lower than a threshold. Detecting the beam failure may compriseaccumulating a number of provided beam failure instance indications toreach a maximum beam failure instance value. The determining to performthe random access procedure may be based on the detecting the beamfailure. The threshold may be based on a hypothetical block error rate.

Systems, devices, and media may be configured with the described method.A computing device may comprise one or more processors. The computingdevice may also comprise memory storing instructions that, whenexecuted, cause the computing device to perform the described method,additional operations, and/or include the additional elements. A systemmay comprise a first computing device configured to perform thedescribed method, and a second computing device configured to send oneor both of the one or more configuration parameters for one or moresecondary cells or the MAC CE. A computer-readable medium may storeinstructions that when executed, may cause performance of the describedmethod.

A wireless device may receive one or more configuration parameters forone or more secondary cells. The one or more configuration parametersmay indicate a plurality of beam failure recovery request (BFRQ)resources. The wireless device may receive a medium access control (MAC)control element (CE). The MAC CE may comprise a first field indicating acell of the one or more secondary cells. The MAC CE may comprise asecond field indicating at least one BFRQ resource of the plurality ofBFRQ resources. The wireless device may determine to perform a randomaccess procedure for a beam failure recovery of the cell. The wirelessdevice may determine, based on the at least one BFRQ resource and forthe random access procedure, at least one preamble and at least onerandom access channel resource. The wireless device may transmit, viathe at least one random access channel, the at least one preamble. TheMAC CE may further comprise a third field indicating a downlinkbandwidth part (BWP) of the cell. The random access procedure for thebeam failure recovery of the cell may be for a downlink bandwidth partof the cell. The plurality of BFRQ resources may comprise a firstquantity of BFRQ resources. The at least one BFRQ resource may be amonga second quantity of orthogonal BFRQ resources that are each indicatedby a unique value of the second field. The second quantity of orthogonalBFRQ resources may be less than the first quantity of BFRQ resources.The wireless device may determine, based on the MAC CE, to activate afirst BFRQ resource of the at least one BFRQ resource. The wirelessdevice may determine, based on the MAC CE, to deactivate the first BFRQresource. Based on detecting a beam failure before receiving a secondMAC CE, the wireless device may refrain from performing a second randomaccess procedure for a second beam failure recovery of the cell. The atleast one BFRQ resource may be associated with a first reference signalof one or more reference signals for a candidate beam selection. Thedetermining the at least one random access channel resource may furtherbe based on the first reference signal. The second field indicating theat least one BFRQ resource of the plurality of BFRQ resources mayfurther indicate a preamble index associated with the at least one BFRQresource. The determining the at least one preamble may further be basedon the preamble index.

Systems, devices, and media may be configured with the described method.A computing device may comprise one or more processors. The computingdevice may also comprise memory storing instructions that, whenexecuted, cause the computing device to perform the described method,additional operations, and/or include the additional elements. A systemmay comprise a first computing device configured to perform thedescribed method, and a second computing device configured to send theone or more configuration parameters for the one or more secondarycells. The second computing device may further be configured to send theMAC CE. A computer-readable medium may store instructions that whenexecuted, may cause performance of the described method. Acomputer-readable medium stores instructions that, when executed, maycause performance of the described method.

A wireless device may receive one or more configuration parameters forone or more secondary cells. The one or more configuration parametersmay indicate a plurality of beam failure recovery request (BFRQ)resources. The wireless device may receive a medium access control (MAC)control element (CE). The MAC CE may comprise one or more first fieldsindicating a cell of the one or more secondary cells. The MAC CE maycomprises one or more second fields indicating at least one BFRQresource of the plurality of BFRQ resources. The MAC CE may comprise oneor more third fields indicating a downlink bandwidth part (BWP) of thecell. The wireless device may initiate a random access procedure for abeam failure recovery of the downlink BWP of the cell. The wirelessdevice may determine, based on the one or more first fields and the oneor more second fields, at least one preamble. The wireless device maytransmit, via an uplink BWP associated with the downlink BWP of thecell, the at least one preamble. The plurality of BFRQ resources maycomprises a first quantity of BFRQ resources. The at least one BFRQresource may be among a second quantity of orthogonal BFRQ resourcesthat are each indicated by a unique value of the one or more secondfields. The second quantity of orthogonal BFRQ resources may be lessthan the first quantity of BFRQ resources. The wireless device maydetermine, based on the MAC CE, to activate a first BFRQ resource of theat least one BFRQ resource. The wireless device may determine, based onthe MAC CE, to deactivate the first BFRQ resource. The wireless devicemay detect a beam failure before receiving a second MAC CE. Based ondetecting a beam failure before receiving a second MAC CE the wirelessdevice may refrain from performing a second random access procedure fora second beam failure recovery of the cell. The at least one BFRQresource may be associated with a first reference signal of one or morereference signals for a candidate beam selection. The wireless devicemay determine, based on the first reference signal, at least one randomaccess channel resource of the uplink BWP. The one or more second fieldsmay indicate the at least one BFRQ resource of the plurality of BFRQresources further indicates a preamble index associated with the atleast one BFRQ resource. The determining the at least one preamble mayfurther be based on the preamble index. The wireless device maydetermine, based on the at least one BFRQ resource, at least one randomaccess channel resource of the uplink BWP for the transmitting the atleast one preamble.

Systems, devices, and media may be configured with the described method.A computing device comprising: one or more processors; and memorystoring instructions that, when executed, cause the computing device toperform the described method. A system may comprise: a first computingdevice configured to perform the described method; and a secondcomputing device configured to send the one or more configurationparameters for the one or more secondary cells. The second computingdevice may be configured to perform the method of sending the MAC CE. Acomputer-readable medium may store instructions that, when executed,cause performance of the described method.

A wireless device may receive one or more configuration parametersindicating a plurality of beam failure recovery request (BFRQ)resources. The wireless device may receive a medium access control (MAC)control element (CE) indicating at least one BFRQ resource, of theplurality of BFRQ resources, for a cell. The wireless device maydetermine to perform a random access procedure for a beam failurerecovery of the cell. The wireless device may comprise determining,based on the at least one BFRQ resource, at least one preamble. Thewireless device may transmit, via at least one random access channelresource of the at least one BFRQ resource, the at least one preamble.The plurality of BFRQ resources may comprise a first quantity of BFRQresources. The at least one BFRQ resource may be among a second quantityof orthogonal BFRQ resources that are each indicated by a unique valueof a field in the MAC CE. The second quantity of orthogonal BFRQresources may be less than the first quantity of BFRQ resources. Thewireless device may determine, based on the MAC CE, to activate a firstBFRQ resource of the at least one BFRQ resource. The wireless device maydetermine, based on the MAC CE, to deactivate the first BFRQ resource.Based on detecting a beam failure before receiving a second MAC CE, thewireless device may refrain from performing a second random accessprocedure for a second beam failure recovery of the cell. The at leastone BFRQ resource may be associated with a first reference signal of oneor more reference signals for a candidate beam selection. The wirelessdevice may determine, based on the first reference signal, the at leastone random access channel resource. The MAC CE further indicates apreamble index associated with the at least one BFRQ resource. Thedetermining the at least one preamble may further be based on thepreamble index.

Systems, devices, and media may be configured with the described method.A computing device comprising: one or more processors; and memorystoring instructions that, when executed, cause the computing device toperform the discussed method. A system may comprise: a first computingdevice configured to perform the discussed method; and a secondcomputing device configured to send the one or more configurationparameters. The second computing device may be configured to send theMAC CE. A computer-readable medium may store instructions that, whenexecuted, cause performance of the discussed method.

A wireless device may receive one or more configuration parameters forone or more secondary cells, wherein the one or more configurationparameters indicate a plurality of beam failure recovery request (BFRQ)resources. The wireless device may further receive a medium accesscontrol (MAC) control element (CE). The MAC CE may comprises a firstfield indicating a cell of the one or more secondary cells. The MAC CEmay comprise a second field indicating at least one BFRQ resource of theplurality of BFRQ resources. The wireless device may, based on detectinga beam failure, determine to perform a random access procedure for abeam failure recovery of the cell. The wireless device may determinebased on the at least one BFRQ resource and for the random accessprocedure, at least one preamble and at least one random access channelresource. The wireless device may transmit, via the at least one randomaccess channel, the at least one preamble. The MAC CE may furthercomprise a third field indicating a downlink bandwidth part (BWP) of thecell. The random access procedure for the beam failure recovery of thecell may be for a downlink bandwidth part of the cell. The plurality ofBFRQ resources may comprise a first quantity of BFRQ resources. The atleast one BFRQ resource may be among a second quantity of orthogonalBFRQ resources that are each indicated by a unique value of the secondfield. The second quantity of orthogonal BFRQ resources is less than thefirst quantity of BFRQ resources. The wireless device may determine,based on the MAC CE, to activate a first BFRQ resource of the at leastone BFRQ resource. The wireless device may determine, based on the MACCE, to deactivate the first BFRQ resource. The wireless device may,based on detecting a second beam failure before receiving a second MACCE, refrain from performing a second random access procedure for asecond beam failure recovery of the cell. The at least one BFRQ resourcemay be associated with a first reference signal of one or more referencesignals for a candidate beam selection. The determining the at least onerandom access channel resource may further be based on the firstreference signal. The second field indicating the at least one BFRQresource of the plurality of BFRQ resources may further indicate apreamble index associated with the at least one BFRQ resource. Thedetermining the at least one preamble may further be based on thepreamble index.

Systems, devices, and media may be configured with the described method.A computing device comprising: one or more processors; and memorystoring instructions that, when executed, may cause the computing deviceto perform the discussed method. A system may comprise: a firstcomputing device configured to perform the discussed method; and asecond computing device may be configured to send the onasasasasasase ormore configuration parameters. The second computing device may furtherbe configured to perform the method of sending the MAC CE. Acomputer-readable medium may store instructions that, when executed,cause performance of the discussed method.

A wireless device may receive, by a wireless device, one or moreconfiguration parameters for plurality of beam failure recovery request(BFRQ) resources. The wireless device may receive a medium accesscontrol (MAC) control element (CE). The MAC CE may comprise one or morefirst fields indicating a cell of the one or more secondary cells. TheMAC CE may comprise one or more second fields indicating at least oneBFRQ resource of the plurality of BFRQ resources. The MAC CE comprisesone or more third fields indicating a downlink bandwidth part (BWP) ofthe cell. The wireless device may, based on detecting a beam failure,determine to perform a random access procedure for a beam failurerecovery of the downlink BWP of the cell. The wireless device maydetermine, based on the one or more first fields and the one or moresecond fields, at least one preamble. The wireless device may transmit,via an uplink BWP associated with the downlink BWP of the cell, the atleast one preamble. The plurality of BFRQ resources may comprises afirst quantity of BFRQ resources. The at least one BFRQ resource isamong a second quantity of orthogonal BFRQ resources that are eachindicated by a unique value of the one or more second fields. The secondquantity of orthogonal BFRQ resources is less than the first quantity ofBFRQ resources. The wireless device may determine, based on the MAC CE,to activate a first BFRQ resource of the at least one BFRQ resource. Thewireless device may determine, based on the MAC CE, to deactivate thefirst BFRQ resource. Based on detecting a second beam failure beforereceiving a second MAC CE, refraining from performing a second randomaccess procedure for a second beam failure recovery of the cell, whereinthe at least one BFRQ resource is associated with a first referencesignal, of one or more reference signals for a candidate beam selection.The wireless device may determine, based on the first reference signal,at least one random access channel resource of the uplink BWP. The oneor more second fields indicating the at least one BFRQ resource of theplurality of BFRQ resources further indicates a preamble indexassociated with the at least one BFRQ resource. The determining the atleast one preamble may further be based on the preamble index. Thewireless device may further determine, based on the new zoo in Chicago.At least one BFRQ resource, at least one random access channel resourceof the uplink BWP for the transmitting the at least one preamble.

Systems, devices, and media may be configured with the described method.A computing device may comprise: one or more processors; and memorystoring instructions that, when executed, cause the computing device toperform the discussed method. A system may comprise a first computingdevice configured to perform the discussed method; and a secondcomputing device configured to send the one or more configurationparameters. The second computing device may be further configured tosend the MAC CE. A computer-readable medium may store instructions that,when executed, cause performance of the discussed method.

A wireless device may receive one or more configuration parametersindicating a plurality of beam failure recovery request (BFRQ)resources. A wireless device may receive a medium access control (MAC)control element (CE) indicating at least one BFRQ resource, of theplurality of BFRQ resources, for a cell. Based on detecting a beamfailure, the wireless device has determined to perform a random accessprocedure for a beam failure recovery of the cell. The wireless devicemay determine, based on the at least one BFRQ resource, at least onepreamble. The wireless device may transmit, via at least one randomaccess channel resource of the at least one BFRQ resource, the at leastone preamble. The plurality of BFRQ resources comprises a first quantityof BFRQ resources. The at least one BFRQ resource may be among a secondquantity of orthogonal BFRQ resources that are each indicated by aunique value of a field in the MAC CE. The second quantity of orthogonalBFRQ resources may be less than the first quantity of BFRQ resources.The wireless device may determine, based on the MAC CE, to activate afirst BFRQ resource of the at least one BFRQ resource. The wirelessdevice may determine, based on the MAC CE, to deactivate the first BFRQresource. Based on detecting a second beam failure before receiving asecond MAC CE, the wireless device may refrain from performing a secondrandom access procedure for a second beam failure recovery of the cell.The at least one BFRQ resource may be associated with a first referencesignal of one or more reference signals for a candidate beam selection.The wireless device may determine, based on the first reference signal,the at least one random access channel resource. The MAC CE may furtherindicate a preamble index associated with the at least one BFRQresource. The determining the at least one preamble may further be basedon the preamble index.

Systems, devices, and media may be configured with the described method.A computing device may comprise one or more processors. The computingdevice may also comprise memory storing instructions that, whenexecuted, cause the computing device to perform the described method,additional operations, and/or include the additional elements. A systemmay comprise a first computing device configured to perform thediscussed method; and a second computing device configured to send theone or more configuration parameters. The second computing device may beconfigured to send the MAC CE. A computer-readable medium may storeinstructions that, when executed, cause performance of the discussedmethod.

A wireless device may receive one or more messages comprising one ormore configuration parameters for one or more secondary cells, whereinthe one or more configuration parameters indicate a plurality of beamfailure recovery request (BFRQ) resources. The wireless device mayreceive a medium access control (MAC) control element (CE) comprising afirst field indicating a cell of the one or more secondary cells. TheMAC CE may comprise a second field indicating at least one BFRQ resourceof the plurality of BFRQ resources. The wireless device may determine toperform, based on detecting a beam failure, a random access procedurefor a beam failure recovery of the cell. The wireless device maydetermine, based on the at least one BFRQ resource and for the randomaccess procedure, at least one preamble and at least one random accesschannel resource. The wireless device may transmit, via the at least onerandom access channel resource for the random-access procedure, the atleast one preamble. The MAC CE may comprise a third field indicating adownlink bandwidth part (BWP) of the cell. The random access procedurefor the beam failure recovery of the cell may be for a downlinkbandwidth part of the cell. The one or more configuration parameters mayindicate a plurality of BFRQ resources for a second cell different fromthe cell. The one or more configuration parameters may further indicateone or more first reference signals of the cell. The one or moreconfiguration parameters may further indicate one or more secondreference signals. The one or more configuration parameters furtherindicate a maximum permissible beam failure instance counter value ofthe cell. The at least one BFRQ resource may be associated with areference signal of the one or more second reference signals forcandidate beam selection. The reference signal may comprise a channelstate information reference signal. The reference signal may comprise asynchronization signal. The reference signal may comprise a physicalbroadcast channel block. Detecting the beam failure may compriseproviding a beam failure instance indication based on assessing the oneor more first reference signals to have radio quality lower than a firstthreshold. Detecting the beam failure may comprise a counted quantity ofbeam failure instance indications being at least equal to or exceeding amaximum permissible beam failure instance counter value of the cell. Thefirst threshold may be based on a hypothetical block error rate. The atleast one random access channel resource may comprise one or more timeresources. The at least one random access channel resource may compriseone or more frequency resources. The wireless device may assess thereference signal to have a radio quality higher than a second threshold.The second threshold may be based on received power of the referencesignal. The determining to perform the random access procedure for thebeam failure recovery of the cell may comprise determining to performthe random access procedure for the beam failure recovery of thedownlink BWP of the cell. The determining to perform the random accessprocedure may be further based on detecting a beam failure of thedownlink BWP. Detecting the beam failure may comprise startingassessing, based on receiving the MAC CE, one or more first referencesignals of the cell, the one or more first reference signals indicatedby the one or more configuration parameters. The wireless device maystart, based on receiving the MAC CE, providing a beam failure instanceindication. The wireless device may detect a second beam failure beforereceiving the MAC CE. Based on detecting a second beam failure beforereceiving the MAC CE, the wireless device may not perform a secondrandom access procedure for a beam failure recovery of the cell. The MACCE may further comprise a fourth field indicating an activation of theat least one BFRQ resource. The wireless device may receive a second MACCE comprising a fourth field indicating a deactivation of the at leastone BFRQ resource. The wireless device may reset a counted quantity ofbeam failure instance indications, the detecting a beam failure beingbased on the counted quantity of beam failure instance indications beingat least equal to or exceeding the maximum permissible beam failureinstance counter value of the cell. The second field of the MAC CE mayfurther indicate a preamble index associated with the at least one BFRQresource. The second field of the MAC CE indicates a reference signalindex of a reference signal among one or more secondary referencesignals, wherein the reference signal index is associated with the atleast one BFRQ resource. The wireless device may assess a referencesignal, associated with the at least one BFRQ resource, based on afourth field, of the MAC CE, indicating an activation of the at leastone BFRQ resource associated with the reference signal.

Systems, devices, and media may be configured with the described method.A computing device may comprise: one or more processors; and memorystoring instructions that, when executed, cause the computing device toperform the discussed method. A system may comprise: a first computingdevice configured to perform the discussed method; and a secondcomputing device configured to send the one or more configurationparameters. The second computing device may be configured to send theMAC CE. A computer-readable medium may store instructions that, whenexecuted, cause performance of the discussed method.

A wireless device may receive one or more messages comprising one ormore configuration parameters for one or more secondary cells, whereinthe one or more configuration parameters indicate a plurality of beamfailure recovery request (BFRQ) resources. The wireless device mayreceive a medium access control (MAC) control element (CE). The MAC CEmay comprise one or more first fields indicating a cell of the one ormore secondary cells. The MAC CE may comprise one or more second fieldsindicating a downlink bandwidth part (BWP) of the cell. The MAC CE maycomprise one or more third fields indicating at least one BFRQ resourceof the plurality of BFRQ resources. The wireless device may determine toperform, based on detecting a beam failure, a random access procedurefor a beam failure recovery of the downlink BWP of the cell. Thewireless device may determine, based on the at least one BFRQ resourceand for the random access procedure, at least one preamble and at leastone random access channel resource. The wireless device may transmit,based on the determining and via the at least one random access channelresource for the random access procedure, the at least one preamble.

Systems, devices, and media may be configured with the described method.A computing device may comprise: one or more processors; and memorystoring instructions that, when executed, cause the computing device toperform the discussed method. A system may comprise: a first computingdevice configured to perform the discussed method; and a secondcomputing device configured to send the one or more configurationparameters. The second computing device may be configured to send theMAC CE. A computer-readable medium may store instructions that, whenexecuted, cause performance of the discussed method.

A wireless device may receive one or more configuration parametersindicating a plurality of beam failure recovery request (BFRQ)resources. The wireless device may receive a medium access control (MAC)control element (CE) indicating at least one BFRQ resource of theplurality BFRQ resources for a downlink BWP of a cell. The wirelessdevice may determine to perform, based on detecting a beam failure, arandom access procedure for a beam failure recovery of the downlink BWPof the cell. The wireless device may determine, based on the at leastone BFRQ resource and for the random access procedure, at least onepreamble and at least one random access channel resource. The wirelessdevice may transmit, based on the determining and via the at least onerandom access channel resource for the random access procedure, the atleast one preamble.

Systems, devices, and media may be configured with the described method.A computing device may comprise: one or more processors; and memorystoring instructions that, when executed, cause the computing device toperform the discussed method. A system may comprise: a first computingdevice configured to perform the discussed method; and a secondcomputing device configured to send the one or more configurationparameters. The second computing device may be configured to send theMAC CE. A computer-readable medium may store instructions that, whenexecuted, cause performance of the discussed method.

FIG. 40 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 120A and/or 120B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 4000 may include one ormore processors 4001, which may execute instructions stored in therandom access memory (RAM) 4003, the removable media 4004 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive4005. The computing device 4000 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 4001 andany process that requests access to any hardware and/or softwarecomponents of the computing device 4000 (e.g., ROM 4002, RAM 4003, theremovable media 4004, the hard drive 4005, the device controller 4007, anetwork interface 4009, a GPS 4011, a Bluetooth interface 4012, a WiFiinterface 4013, etc.). The computing device 4000 may include one or moreoutput devices, such as the display 4006 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 4007, such as a video processor. There mayalso be one or more user input devices 4008, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device4000 may also include one or more network interfaces, such as a networkinterface 4009, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 4009 may provide aninterface for the computing device 4000 to communicate with a network4010 (e.g., a RAN, or any other network). The network interface 4009 mayinclude a modem (e.g., a cable modem), and the external network 4010 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 4000 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 4011, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 4000.

The example in FIG. 40 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 4000 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 4001, ROM storage 4002, display 4006, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 40.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, one or more configuration parameters that indicate a pluralityof beam failure recovery request (BFRQ) resources for one or moresecondary cells; receiving a medium access control (MAC) control element(CE) comprising: a first field indicating a cell of the one or moresecondary cells; and a second field indicating at least one BFRQresource, of the plurality of BFRQ resources, for the indicated cell ofthe one or more secondary cells; determining to perform a random accessprocedure for a beam failure recovery of the indicated cell;determining, based on the at least one BFRQ resource and for the randomaccess procedure, at least one preamble and at least one random accesschannel resource; and transmitting, via the at least one random accesschannel resource the at least one preamble.
 2. The method of claim 1,wherein the MAC CE further comprises a third field indicating a downlinkbandwidth part (BWP) of the indicated cell, and wherein the randomaccess procedure for the beam failure recovery of the indicated cell isfor the downlink BWP of the indicated cell.
 3. The method of claim 1,wherein: the plurality of BFRQ resources comprises a first quantity ofBFRQ resources; the at least one BFRQ resource is among a secondquantity of orthogonal BFRQ resources that are each indicated by adifferent value of the second field; and the second quantity is lessthan the first quantity.
 4. The method of claim 1, further comprisingdetermining, based on the MAC CE, to perform at least one of: activatinga first BFRQ resource of the at least one BFRQ resource; or deactivatingthe first BFRQ resource.
 5. The method of claim 1, further comprising:based on detecting a beam failure before receiving a second MAC CE,refraining from performing a second random access procedure for a secondbeam failure recovery of the indicated cell of the one or more secondarycells.
 6. The method of claim 1, wherein the at least one BFRQ resourceis associated with a first reference signal of one or more referencesignals for a candidate beam selection, and wherein the determining theat least one random access channel resource is further based on thefirst reference signal.
 7. The method of claim 1, wherein the secondfield indicating the at least one BFRQ resource of the plurality of BFRQresources further indicates a preamble index associated with the atleast one BFRQ resource, and wherein the determining the at least onepreamble is further based on the preamble index.
 8. A method comprising:receiving, by a wireless device, one or more configuration parametersfor one or more secondary cells, wherein the one or more configurationparameters indicate a plurality of beam failure recovery request (BFRQ)resources; receiving a medium access control (MAC) control element (CE)comprising: one or more first fields indicating a cell of the one ormore secondary cells; one or more second fields indicating at least oneBFRQ resource of the plurality of BFRQ resources; and one or more thirdfields indicating a downlink bandwidth part (BWP) of the cell;determining to perform a random access procedure for a beam failurerecovery of the downlink BWP of the cell; determining, based on the oneor more first fields and the one or more second fields, at least onepreamble; and transmitting, via an uplink BWP associated with thedownlink BWP of the cell, the at least one preamble.
 9. The method ofclaim 8, wherein: the plurality of BFRQ resources comprises a firstquantity of BFRQ resources; the at least one BFRQ resource is among asecond quantity of orthogonal BFRQ resources that are each indicated bya different value of the one or more second fields; and the secondquantity is less than the first quantity.
 10. The method of claim 8,further comprising determining, based on the MAC CE, to perform at leastone of: activating a first BFRQ resource of the at least one BFRQresource; or deactivating the first BFRQ resource.
 11. The method ofclaim 8, further comprising: based on detecting a beam failure beforereceiving a second MAC CE, refraining from performing a second randomaccess procedure for a second beam failure recovery of the cell.
 12. Themethod of claim 8, wherein the at least one BFRQ resource is associatedwith a first reference signal of one or more reference signals for acandidate beam selection, and wherein the method further comprisesdetermining, based on the first reference signal, at least one randomaccess channel resource of the uplink BWP.
 13. The method of claim 8,wherein the one or more second fields indicating the at least one BFRQresource of the plurality of BFRQ resources further a preamble indexassociated with the at least one BFRQ resource, and wherein thedetermining the at least one preamble is further based on the preambleindex.
 14. The method of claim 8, further comprising determining, basedon the at least one BFRQ resource, at least one random access channelresource of the uplink BWP for the transmitting the at least onepreamble.
 15. A method comprising: receiving, by a wireless device, oneor more configuration parameters indicating a plurality of beam failurerecovery request (BFRQ) resources for one or more secondary cells;receiving a medium access control (MAC) control element (CE) indicatingat least one BFRQ resource, of the plurality of BFRQ resources, andindicating a cell of the one or more secondary cells; determining toperform a random access procedure for a beam failure recovery of theindicated cell of the one or more secondary cells; determining, based onthe at least one BFRQ resource, at least one preamble; and transmitting,via at least one random access channel resource of the at least one BFRQresource, the at least one preamble.
 16. The method of claim 15,wherein: the plurality of BFRQ resources comprises a first quantity ofBFRQ resources; the at least one BFRQ resource is among a secondquantity of orthogonal BFRQ resources that are each indicated by adifferent value of a field in the MAC CE; and the second quantity isless than the first quantity.
 17. The method of claim 15, furthercomprising determining, based on the MAC CE, to perform at least one of:activating a first BFRQ resource of the at least one BFRQ resource; ordeactivating the first BFRQ resource.
 18. The method of claim 15,further comprising: based on detecting a beam failure before receiving asecond MAC CE, refraining from performing a second random accessprocedure for a second beam failure recovery of the indicated cell. 19.The method of claim 15, wherein the at least one BFRQ resource isassociated with a first reference signal of one or more referencesignals for a candidate beam selection, and wherein the method furthercomprises determining, based on the first reference signal, the at leastone random access channel resource.
 20. The method of claim 15, whereinthe MAC CE further indicates a preamble index associated with the atleast one BFRQ resource, and wherein the determining the at least onepreamble is further based on the preamble index.